From: Kishore Batta <kishore.batta@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Josh Boyer <jwboyer@kernel.org>
Cc: linux-firmware@kernel.org
Subject: Re: [PULL]: Revert QDU100 firmware binaries
Date: Tue, 28 Oct 2025 14:25:29 +0530 [thread overview]
Message-ID: <e8ef97f3-8f2d-475f-a283-2e39b8effa32@oss.qualcomm.com> (raw)
In-Reply-To: <b3a1d843-6e64-4573-8afd-edb10ab8e86e@oss.qualcomm.com>
On 10/25/2025 5:22 AM, Dmitry Baryshkov wrote:
> On 24/10/2025 19:24, Josh Boyer wrote:
>> On Fri, Oct 24, 2025 at 5:49 AM Kishore Batta
>> <kishore.batta@oss.qualcomm.com> wrote:
>>>
>>> Hi,
>>>
>>> This is an updated pull request to reflect a corrected commit message.
>>>
>>> The following changes since commit
>>> 19731a36222e7b1ca09be090a19bfd89640a837f:
>>>
>>> Merge branch 'HP_Linux_Firmware_20251023' into 'main' (2025-10-23
>>> 13:30:10 +0000)
>>>
>>> are available in the Git repository at:
>>>
>>> https://github.com/kishorebatta-ossqcom/del_linux_firmware.git
>>> del_firmware
>>
>> We can merge this, but the firmware is already released and included
>> in a number of distributions. Deleting it in the upstream repo isn't
>> going to remediate the license situation.
>>
>> Which platforms is this going to break and how will it show up to the
>> user?
> It will only break the QDU100 platform. I don't know the spread of the
> device, but it is a 5G RAN platform, so it'd not a widespread device.
>
> Nevertheless, I don't think that just deleting the firmware is a
> proper solution for the situation.
>
We are checking with LOST team internally. I will get back on this soon.
next prev parent reply other threads:[~2025-10-28 8:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-24 9:37 [PULL]: Revert QDU100 firmware binaries due to licensing concerns Kishore Batta
2025-10-24 9:49 ` [PULL]: Revert QDU100 firmware binaries Kishore Batta
2025-10-24 16:24 ` Josh Boyer
2025-10-24 23:52 ` Dmitry Baryshkov
2025-10-28 8:55 ` Kishore Batta [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-12-18 15:18 Kishore Batta
2025-12-18 16:31 ` Dmitry Baryshkov
2026-01-02 6:27 ` Kishore Batta
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=e8ef97f3-8f2d-475f-a283-2e39b8effa32@oss.qualcomm.com \
--to=kishore.batta@oss.qualcomm.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=jwboyer@kernel.org \
--cc=linux-firmware@kernel.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