From: "Tom Hochstein" <tom.hochstein@nxp.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] linux-firmware: add firmware files for NXP BT chipsets
Date: Tue, 29 Aug 2023 05:08:32 -0700 [thread overview]
Message-ID: <29102.1693310912640920508@lists.openembedded.org> (raw)
In-Reply-To: <DB3PR0402MB38529DF900F5D80085F17E23E2E3A@DB3PR0402MB3852.eurprd04.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 372 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 451 bytes --]
next prev parent reply other threads:[~2023-08-29 12:08 UTC|newest]
Thread overview: 5+ 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 [this message]
2023-09-05 17:41 ` Tom Hochstein
2023-09-05 23:08 ` [OE-core] " Alexandre Belloni
2023-08-24 20:03 Tom Hochstein
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=29102.1693310912640920508@lists.openembedded.org \
--to=tom.hochstein@nxp.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 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.