Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC][PATCH] module-base.bbclass: keep PR if MACHINE_KERNEL_PR is not set
Date: Fri, 14 May 2010 19:34:13 +0200	[thread overview]
Message-ID: <hsk1il$v4j$2@dough.gmane.org> (raw)
In-Reply-To: <4BED85C7.8000909@eukrea.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 14-05-10 19:17, Eric Bénard wrote:
> Le 14/05/2010 17:52, Koen Kooi a écrit :
>> Op 14 mei 2010, om 17:10 heeft Eric Bénard het volgende geschreven:
>>> I was told you are the person to contact about MACHINE_KERNEL_PR so
>>> may you please have a look to the patch below - also available here :
>>> http://patchwork.openembedded.org/patch/2012/
>>>
>>> Actually, when compiling modules (out of tree), we loose PR if
>>> MACHINE_KERNEL_PR is not set.
>>
>> I don't believe that when MACHINE_KERNEL_PR isn't set people care
>> about PR.
>>
> Does that mean that policy is that MACHINE_KERNEL_PR should be set for
> every machine ?
> If yes, maybe this should be added in the doc.

IMO yes, but some people were against it. Either their kernel never
changes or they don't care about out-of-tree modules breaking on kernel
changes.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFL7YmVMkyGM64RGpERAsf2AJ45yUaAIVL0HCm7jCfxwkmq9C5gnACfcV8w
vGcI7BJka3fCXJJ+RL3Y+Yc=
=RLGB
-----END PGP SIGNATURE-----




  reply	other threads:[~2010-05-14 17:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-03 21:21 [PATCH] module-base.bbclass: keep PR if MACHINE_KERNEL_PR is not set Eric Benard
2010-05-12 15:34 ` Eric Bénard
2010-05-14 15:10 ` [RFC][PATCH] " Eric Bénard
2010-05-14 15:52   ` Koen Kooi
2010-05-14 17:17     ` Eric Bénard
2010-05-14 17:34       ` Koen Kooi [this message]
2010-05-14 17:45         ` Eric Bénard
2010-05-14 19:55           ` Phil Blundell
2010-05-14 20:15             ` Eric Bénard
2010-05-14 21:02               ` Phil Blundell
2010-05-17  7:12                 ` Eric Bénard
2010-05-17  8:02                   ` Phil Blundell
2010-05-14 16:25   ` Phil Blundell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='hsk1il$v4j$2@dough.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox