From: Andreas Oberritter <obi@opendreambox.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: MACHINE_KERNEL_PR overrides PR for modules
Date: Thu, 24 Mar 2011 17:22:12 +0100 [thread overview]
Message-ID: <4D8B6FB4.1040906@opendreambox.org> (raw)
In-Reply-To: <4D8B6AB8.8030300@cbnco.com>
On 03/24/2011 05:00 PM, Michael Smith wrote:
> Andreas Oberritter wrote:
>> how about this solution? For MACHINE_KERNEL_PR = "r11" and PR = "r20" it
>> creates PR = "r11.20", to mimic the revision numbers commonly seen with
>> recipes using INC_PR.
>
> I'd rather see PR before MACHINE_KERNEL_PR as PR seems more "major". But
> like either way better than the current situation.
Actually, that's what I'd prefer, too. But I wanted to provide a
seamless upgrade path, as suggested by Frans.
I'm just starting to use MACHINE_KERNEL_PR, so for me there would be no
big difference either way.
One minor thing: If MACHINE_KERNEL_PR comes last, then
MACHINE_KERNEL_PR_append_local will IMO yield a nicer result.
In the meantime, I've sent an updated patch, moving the code to its own
bbclass file.
Regards,
Andreas
next prev parent reply other threads:[~2011-03-24 16:24 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 [this message]
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
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=4D8B6FB4.1040906@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