From: Tom Rini <tom_rini@mentor.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: [PATCH 3/3] bluez4: Add 4.91 and make it default for Angstrom
Date: Mon, 25 Apr 2011 12:05:38 -0700 [thread overview]
Message-ID: <4DB5C602.60703@mentor.com> (raw)
In-Reply-To: <1303757678.15311.113.camel@mattotaupa>
On 04/25/2011 11:54 AM, Paul Menzel wrote:
> Dear Tom,
>
>
> On Mo, 2011-04-25 at 11:31 -0700, Tom Rini wrote:
>
> what build configuration did you use for build testing? Could you add
> that to the commit message please.
Done.
>> Signed-off-by: Tom Rini <tom_rini@mentor.com>
>> ---
>> recipes/bluez/bluez4_4.91.bb | 18 ++++++++++++++++++
>> 1 files changed, 18 insertions(+), 0 deletions(-)
>> create mode 100644 recipes/bluez/bluez4_4.91.bb
>>
>> diff --git a/recipes/bluez/bluez4_4.91.bb b/recipes/bluez/bluez4_4.91.bb
>> new file mode 100644
>> index 0000000..16f06d5
>> --- /dev/null
>> +++ b/recipes/bluez/bluez4_4.91.bb
>> @@ -0,0 +1,18 @@
>> +require bluez4.inc
>> +
>> +SRC_URI[md5sum] = "3059b7ef5168c84cd0c6a67034ce79f9"
>> +SRC_URI[sha256sum] = "11e9279e2669db996afd464b96d2c68f41f157f6eb9b8842a0bbcad8a4eac18d"
>> +
>> +DEFAULT_PREFERENCE = "-1"
>> +DEFAULT_PREFERENCE_angstrom = "1"
>> +
>> +DEPENDS += "libsndfile1"
>> +
>> +PR = "${INC_PR}.0"
>> +
>> +# Not all distros have a recent enough udev
>> +BTUDEV = " --disable-udevrules"
>> +BTUDEV_angstrom = " --enable-udevrules"
>> +BTUDEV_shr = " --enable-udevrules"
>> +
>> +EXTRA_OECONF += "${BTUDEV}"
>
> Please create the patch next time adding `-M -C -C` to `git
> format-patch`.
Is there a way to shove that into ~/.gitconfig? Otherwise I'm sure to
forget.
> Additionally adding the recipe and making it default for
> Ȧngström could have been two commits in my opinion.
That's a little excessive I think, just because it's largely a given
that Angstrom (and SHR) will be opting to use this and it doesn't add
anything to the bisect'ability of the tree.
> Acked-by: Paul Menzel <paulepanter@users.sourceforge.net>
Just for this one patch I assume.
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2011-04-25 19:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-25 18:31 [RFC, PATCH] Add minver/maxver to patch.bbclass, update bluez Tom Rini
2011-04-25 18:31 ` [PATCH 1/3] patch.bbclass: Add minver/maxver params Tom Rini
2011-04-25 18:31 ` [PATCH 2/3] bluez4.inc: List 4.90 as the maxver for applying a patch Tom Rini
2011-04-25 18:31 ` [PATCH 3/3] bluez4: Add 4.91 and make it default for Angstrom Tom Rini
2011-04-25 18:33 ` Koen Kooi
2011-04-25 18:43 ` Martin Jansa
2011-04-25 18:54 ` Paul Menzel
2011-04-25 19:05 ` Tom Rini [this message]
2011-04-25 19:18 ` Eric Bénard
2011-04-25 20:14 ` [RFC, PATCH] Add minver/maxver to patch.bbclass, update bluez Frans Meulenbroeks
2011-04-25 20:40 ` Tom Rini
2011-04-25 20:52 ` Frans Meulenbroeks
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=4DB5C602.60703@mentor.com \
--to=tom_rini@mentor.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.