Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: "Eric Bénard" <eric@eukrea.com>
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 22:15:41 +0200	[thread overview]
Message-ID: <4BEDAF6D.5010704@eukrea.com> (raw)
In-Reply-To: <1273866959.4465.5.camel@lenovo.internal.reciva.com>

Le 14/05/2010 21:55, Phil Blundell a écrit :
> On Fri, 2010-05-14 at 19:45 +0200, Eric Bénard wrote:
>> so why not setting r0 as a default in bitbake.conf as a compromise ?
>
> A default MACHINE_KERNEL_PR, you mean?  That would cause PR to suddenly
> go backwards for a whole bunch of machines, which would definitely not
> be a good thing.  See the mailing list archive; there was quite a lot of
> discussion of these kinds of issues at the time that the M_K_PR change
> was originally landed.
>
yes, in this case MACHINE_KERNEL_PR would overide kernel's PR which is 
not what we want.

So actually the fix I propose is needed as while MACHINE_KERNEL_PR is 
not required by policy, module-base.bbclass is broken for machines 
without MACHINE_KERNEL_PR.

Eric



  reply	other threads:[~2010-05-14 20:26 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
2010-05-14 17:45         ` Eric Bénard
2010-05-14 19:55           ` Phil Blundell
2010-05-14 20:15             ` Eric Bénard [this message]
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=4BEDAF6D.5010704@eukrea.com \
    --to=eric@eukrea.com \
    --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