From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] udev-extraconf: drop allarch to allow setting to MACHINE_ARCH in some .bbappend
Date: Sun, 25 Nov 2012 20:38:40 +0000 [thread overview]
Message-ID: <1353875920.21863.23.camel@ted> (raw)
In-Reply-To: <1352976932-4150-1-git-send-email-Martin.Jansa@gmail.com>
On Thu, 2012-11-15 at 11:55 +0100, Martin Jansa wrote:
> * if bsp needs some special rule for udev
> * see https://bugzilla.yoctoproject.org/show_bug.cgi?id=3390 for details
>
> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
> ---
> meta/recipes-core/udev/udev-extraconf_1.0.bb | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
I've been thinking about this and some other related problems. There is
a pattern and we need to be able to inherit allarch but disable it's
functionality.
I've therefore just posted an alternative proposed fix for this.
Cheers,
Richard
prev parent reply other threads:[~2012-11-26 9:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 10:55 [PATCH 1/2] udev-extraconf: drop allarch to allow setting to MACHINE_ARCH in some .bbappend Martin Jansa
2012-11-15 10:55 ` [PATCH 2/2] opkg: drop PACKAGE_ARCH setting for update-alternatives-cworth Martin Jansa
2012-11-25 20:38 ` Richard Purdie [this message]
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=1353875920.21863.23.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@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