From: Mario Limonciello <superm1@kernel.org>
To: Josh Boyer <jwboyer@kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Dikshita Agarwal <dikshita.agarwal@oss.qualcomm.com>,
linux-firmware@kernel.org,
Vikash Garodia <vikash.garodia@oss.qualcomm.com>
Subject: Re: add video firmware for Kaanapali
Date: Thu, 2 Oct 2025 08:29:47 -0500 [thread overview]
Message-ID: <e7f5f6ea-ebbd-4454-9adb-2df9e3e7630d@kernel.org> (raw)
In-Reply-To: <CA+5PVA6gN4M7gchGXPoswHmv7h0NiZ_n063r1GOGGVAujdDbKQ@mail.gmail.com>
On 10/2/25 7:19 AM, Josh Boyer wrote:
> On Wed, Oct 1, 2025 at 8:48 PM Dmitry Baryshkov
> <dmitry.baryshkov@oss.qualcomm.com> wrote:
>>
>> On Wed, Oct 01, 2025 at 06:36:11PM +0530, Dikshita Agarwal wrote:
>>> Hi,
>>>
>>> The following changes since commit ed924f6db3c973f941fd6c6317c0d52664e83e5a:
>>>
>>> Merge branch 'robot/pr-0-1759253351' into 'main' (2025-09-30 17:36:46 +0000)
>>>
>>> are available in the Git repository at:
>>>
>>> https://git.codelinaro.org/clo/linux-kernel/linux-firmware.git
>>> video-fw-kaanapali
>>>
>>> for you to fetch changes up to 7c2d4d41e96fdddfa360c0740e8a8ee9b5efb572:
>>>
>>> qcom: vpu: add video firmware for Kaanapali (2025-10-01 18:32:02 +0530)
>>
>> +Link: qcom/vpu/vpu40_p2.mbn -> vpu40_p2_s7.mbn
>>
>> Can we please drop that link? FWIW the driver for that platform is not
>> yet merged.
>
> This got merged yesterday.
>
> https://gitlab.com/kernel-firmware/linux-firmware/-/merge_requests/717
>
> josh
Please send up a pull request to drop the link if it's not correct.
next prev parent reply other threads:[~2025-10-02 13:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-01 13:06 add video firmware for Kaanapali Dikshita Agarwal
2025-10-02 0:48 ` Dmitry Baryshkov
2025-10-02 12:19 ` Josh Boyer
2025-10-02 13:29 ` Mario Limonciello [this message]
2025-10-03 1:04 ` Dmitry Baryshkov
2025-10-03 6:54 ` Dikshita Agarwal
2025-10-03 14:22 ` Dmitry Baryshkov
2025-10-03 15:38 ` Dikshita Agarwal
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=e7f5f6ea-ebbd-4454-9adb-2df9e3e7630d@kernel.org \
--to=superm1@kernel.org \
--cc=dikshita.agarwal@oss.qualcomm.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=jwboyer@kernel.org \
--cc=linux-firmware@kernel.org \
--cc=vikash.garodia@oss.qualcomm.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 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.