From: Phil Blundell <pb@pbcl.net>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] bluez-dtl1-workaround: remove PRIORITY
Date: Tue, 05 Jul 2011 16:54:18 +0100 [thread overview]
Message-ID: <1309881259.2410.16.camel@phil-desktop> (raw)
In-Reply-To: <1309881139.2410.14.camel@phil-desktop>
Or an alternative patch might be just to delete this recipe altogether.
Its sole purpose is to work around defects in hardware which must be the
best part of a decade old and I would be slightly surprised if anyone
was still using DTL1s in this day and age.
p.
On Tue, 2011-07-05 at 16:52 +0100, Phil Blundell wrote:
> This one evaded the earlier mass removal due to extraneous trailing
> whitespace.
>
> Signed-off-by: Phil Blundell <philb@gnu.org>
> ---
> .../bluez/bluez-dtl1-workaround_1.0.bb | 3 +--
> 1 files changed, 1 insertions(+), 2 deletions(-)
>
> diff --git a/meta/recipes-connectivity/bluez/bluez-dtl1-workaround_1.0.bb b/meta/recipes-connectivity/bluez/bluez-dtl1-workaround_1.0.bb
> index b6b3d7d..103cfd9 100644
> --- a/meta/recipes-connectivity/bluez/bluez-dtl1-workaround_1.0.bb
> +++ b/meta/recipes-connectivity/bluez/bluez-dtl1-workaround_1.0.bb
> @@ -1,8 +1,7 @@
> DESCRIPTION = "A nasty hack for for dtl1-cs driver to workaround suspend/resume."
> LICENSE = "GPLv2"
> LIC_FILES_CHKSUM = "file://COPYING;md5=393a5ca445f6965873eca0259a17f833"
> -SECTION = "console"
> -PRIORITY = "optional"
> +SECTION = "console"
> PR = "r3"
>
> SRC_URI = "file://02dtl1_cs.sh \
next prev parent reply other threads:[~2011-07-05 15:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 15:52 [PATCH] bluez-dtl1-workaround: remove PRIORITY Phil Blundell
2011-07-05 15:54 ` Phil Blundell [this message]
2011-07-05 16:31 ` Paul Eggleton
2011-07-05 17:05 ` Koen Kooi
2011-07-05 18:37 ` Phil Blundell
2011-07-06 14:06 ` Paul Eggleton
2011-07-06 23:39 ` Saul Wold
2011-07-07 14:51 ` Phil Blundell
2011-07-07 15:11 ` Paul Eggleton
2011-07-07 16:06 ` Phil Blundell
2011-07-08 15:19 ` Darren Hart
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=1309881259.2410.16.camel@phil-desktop \
--to=pb@pbcl.net \
--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