From: "Vivek Puar" <vpuar@qti.qualcomm.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] linux-firmware: upgrade 20260110 -> 20260221
Date: Mon, 23 Feb 2026 21:09:43 -0800 [thread overview]
Message-ID: <115433.1771909783724444949@lists.openembedded.org> (raw)
In-Reply-To: <hc77r3vu25x7l3vn55xoip2ngmvl4kkdtnddvnfkzqtotizs44@iqx6blwuhp6n>
[-- Attachment #1: Type: text/plain, Size: 172 bytes --]
On Tue, Feb 24, 2026 at 12:13 AM, Dmitry Baryshkov wrote:
>
> I think, I fixed all your comments in v2. Could you please check?
Yes, all fixed.
Regards,
Vivek
[-- Attachment #2: Type: text/html, Size: 256 bytes --]
prev parent reply other threads:[~2026-02-24 5:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-22 21:21 [PATCH] linux-firmware: upgrade 20260110 -> 20260221 Dmitry Baryshkov
2026-02-23 5:21 ` Vivek Puar
2026-02-23 5:28 ` Vivek Puar
2026-02-23 18:43 ` Dmitry Baryshkov
2026-02-24 5:09 ` Vivek Puar [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=115433.1771909783724444949@lists.openembedded.org \
--to=vpuar@qti.qualcomm.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