From: Andreas Oberritter <obi@opendreambox.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCHv2] kernel/module-base: Append PR to MACHINE_KERNEL_PR
Date: Tue, 05 Apr 2011 11:08:29 +0200 [thread overview]
Message-ID: <4D9ADC0D.6060603@opendreambox.org> (raw)
In-Reply-To: <inecec$sae$2@dough.gmane.org>
On 04/05/2011 08:22 AM, Koen Kooi wrote:
> On 04-04-11 20:12, Andreas Oberritter wrote:
>> On 04/04/2011 07:54 PM, Koen Kooi wrote:
>>> On 04-04-11 17:14, Andreas Oberritter wrote:
>>>> On 04/04/2011 03:58 PM, Koen Kooi wrote:
>>>>> On 04-04-11 15:00, Andreas Oberritter wrote:
>>>>>> Ping. Any votes for or against this patch with either appended or
>>>>>> prepended PR?
>>>>>
>>>>> I don't like this patch *at all*. Recipes can already do
>>>>> MACHINE_KERNEL_PR_append = "something" if they need to.
>>>
>>>> The use of MACHINE_KERNEL_PR is optional, so it feels really wrong to
>>>> append something to it in a recipe.
>>>
>>>>> Can you should me a specific example on how this would be an improvement?
>>>
>>>> With the version below. a distro can start to use MACHINE_KERNEL_PR any
>>>> time without breaking updates.
>>>
>>>> The vast majority of modules do not use MACHINE_KERNEL_PR
>>>
>>> It seems you don't understand how MACHINE_KERNEL_PR works. The *machine*
>>> sets it. The distro has *no* say in it. Therefore the module recipes
>>> don't need to set it, since it's automatic.
>
>> That's nitpicking. Let me rephrase:
>
>> With the previously cited version. a *machine* can start to use
>> MACHINE_KERNEL_PR any time without breaking updates.
>
>> The vast majority of module recipes do not use MACHINE_KERNEL_PR. That
>> means that they use their own PR instead of appending something to
>> MACHINE_KERNEL_PR, as suggested by you. Setting MACHINE_KERNEL_PR in the
>> machine's configuration disables automatic rebuilds of 91% of module
>> recipes.
>
> So make all the module recipes use MACHINE_KERNEL_PR and ditch PR.
Thereby making MACHINE_KERNEL_PR mandatory for all machines?
next prev parent reply other threads:[~2011-04-05 9:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-20 9:59 MACHINE_KERNEL_PR overrides PR for modules Denis Dydychkin
2011-02-20 10:40 ` Graeme Gregory
2011-02-20 11:26 ` Frans Meulenbroeks
2011-03-24 15:37 ` Andreas Oberritter
2011-03-24 16:00 ` Michael Smith
2011-03-24 16:22 ` Andreas Oberritter
2011-03-24 15:37 ` [PATCH] kernel/module-base: Append PR to MACHINE_KERNEL_PR Andreas Oberritter
2011-03-24 16:14 ` [PATCHv2] " Andreas Oberritter
2011-04-04 13:00 ` Andreas Oberritter
2011-04-04 13:58 ` Koen Kooi
2011-04-04 15:14 ` Andreas Oberritter
2011-04-04 17:54 ` Koen Kooi
2011-04-04 18:12 ` Tom Rini
2011-04-04 18:12 ` Andreas Oberritter
2011-04-05 6:22 ` Koen Kooi
2011-04-05 9:08 ` Andreas Oberritter [this message]
2011-04-05 9:23 ` Koen Kooi
2011-04-05 9:32 ` Phil Blundell
2011-04-05 10:39 ` Koen Kooi
2011-04-05 10:58 ` Phil Blundell
2011-04-05 11:31 ` Frans Meulenbroeks
2011-04-05 22:33 ` Mike Westerhof
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=4D9ADC0D.6060603@opendreambox.org \
--to=obi@opendreambox.org \
--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