public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Quentin Schulz <quentin.schulz@cherry.de>
To: Dmitry Baryshkov <dbaryshkov@gmail.com>
Cc: openembedded-core@lists.openembedded.org,
	Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [OE-core] [scarthgap][PATCH v2] linux-firmware: add a package for ath12k firmware
Date: Tue, 27 Aug 2024 13:38:18 +0200	[thread overview]
Message-ID: <3740ffde-e3c2-45db-8de4-e968dba578d0@cherry.de> (raw)
In-Reply-To: <CALT56yNt9cFULbzMpSz7sBXzS9+b-=K7JnvBLUKWvJ6ieUniTA@mail.gmail.com>

Hi Dmitry,

On 8/27/24 1:37 PM, Dmitry Baryshkov wrote:
> On Tue, 27 Aug 2024 at 14:32, Quentin Schulz <quentin.schulz@cherry.de> wrote:
>>
>> Hi Dmitry,
>>
>> On 8/27/24 12:03 PM, Dmitry Baryshkov via lists.openembedded.org wrote:
>>> From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
>>>
>>> Add the firmware package for the ATH12K module.
>>>
>>> Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
>>> [DB: added rdepends from PN to PN-ath12k]
>>> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
>>> ---
>>>
>>> Changes since v1:
>>>    - Added PN-ath12k to RDEPENDS:PN as not to break users expecting ath12k
>>>      from linux-firmware (Quentin Schulz)
>>>
>>
>> Was it really part of the linux-firmware package? I hadn't checked
>> myself, it was an assumption.
> 
> Yes, it wasn't split to any of the packages, so it was in ${PN}.
> 

ACK.

Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>

Thanks!
Quentin


      reply	other threads:[~2024-08-27 11:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-27 10:03 [scarthgap][PATCH v2] linux-firmware: add a package for ath12k firmware Dmitry Baryshkov
2024-08-27 11:32 ` [OE-core] " Quentin Schulz
2024-08-27 11:37   ` Dmitry Baryshkov
2024-08-27 11:38     ` Quentin Schulz [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=3740ffde-e3c2-45db-8de4-e968dba578d0@cherry.de \
    --to=quentin.schulz@cherry.de \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=dbaryshkov@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