Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Tom Hochstein <tom.hochstein@nxp.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] linux-firmware: add firmware files for NXP BT chipsets
Date: Wed, 6 Sep 2023 01:08:30 +0200	[thread overview]
Message-ID: <20230905230830dd3380ae@mail.local> (raw)
In-Reply-To: <24144.1693935708896928880@lists.openembedded.org>

On 05/09/2023 10:41:48-0700, Tom Hochstein wrote:
> On Tue, Aug 29, 2023 at 05:08 AM, Tom Hochstein wrote:
> 
> > 
> > On Fri, Aug 25, 2023 at 07:37 AM, Tom Hochstein wrote:
> > 
> >> Please hold off on this. The -common design is not working correctly and
> >> is causing those firmware packages to be registered as a runtime
> >> dependency of the main package.
> > 
> > 
> > 
> > Actually, the -common design is working fine, there was just a
> > misunderstanding.
> > 
> > Please do consider this patch as-is.
> > 
> > Tom
> > 
> > 
> > 
> 
> Ping

Please rebase and submit v2

> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#187250): https://lists.openembedded.org/g/openembedded-core/message/187250
> Mute This Topic: https://lists.openembedded.org/mt/100943055/3617179
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [alexandre.belloni@bootlin.com]
> -=-=-=-=-=-=-=-=-=-=-=-
> 


-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


      reply	other threads:[~2023-09-05 23:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <177E6A5CBC11CE3B.14626@lists.openembedded.org>
2023-08-25 14:37 ` [OE-core] [PATCH] linux-firmware: add firmware files for NXP BT chipsets Tom Hochstein
2023-08-29 12:08   ` Tom Hochstein
2023-09-05 17:41     ` Tom Hochstein
2023-09-05 23:08       ` Alexandre Belloni [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=20230905230830dd3380ae@mail.local \
    --to=alexandre.belloni@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=tom.hochstein@nxp.com \
    /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