From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Guixin Liu <kanie@linux.alibaba.com>
Cc: "Bjorn Helgaas" <helgaas@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
linux-pci@vger.kernel.org,
"Xunlei Pang" <xlpang@linux.alibaba.com>,
oliver.yang@linux.alibaba.com
Subject: Re: [PATCH v11 0/2] PCI: Fix crash when access broken ROM
Date: Fri, 24 Apr 2026 11:38:54 +0300 [thread overview]
Message-ID: <aessHrL4jkCbSjNA@ashevche-desk.local> (raw)
In-Reply-To: <e607705c-b4eb-4582-b941-28e9a318dbe2@linux.alibaba.com>
On Fri, Apr 24, 2026 at 02:32:06PM +0800, Guixin Liu wrote:
> 在 2026/2/10 01:54, Bjorn Helgaas 写道:
> > On Mon, Feb 09, 2026 at 02:43:39PM +0800, Guixin Liu wrote:
...
> > > In this version, I fixed the case issues in the first patch title.
> > Will do, thanks. Since the v7.0 merge window is open, this is on my
> > list to look at as soon as v7.0-rc1 is tagged, probably on Feb 22.
> Hi Bjorn, looks like these two patches still haven't been merged, Would it
> be possible to get them merged for the 7.0 release?
v7.0 has already been released. Now it's a v7.1-rc1 candidate at best.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-04-24 8:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 8:07 [PATCH v11 0/2] PCI: Fix crash when access broken ROM Guixin Liu
2026-01-30 8:07 ` [PATCH v11 1/2] PCI: Introduce named defines for PCI ROM Guixin Liu
2026-05-02 16:55 ` Krzysztof Wilczyński
2026-05-06 4:40 ` Guixin Liu
2026-01-30 8:07 ` [PATCH v11 2/2] PCI: Check ROM header and data structure addr before accessing Guixin Liu
2026-04-30 21:46 ` Bjorn Helgaas
2026-05-06 4:39 ` Guixin Liu
2026-02-09 6:43 ` [PATCH v11 0/2] PCI: Fix crash when access broken ROM Guixin Liu
2026-02-09 17:54 ` Bjorn Helgaas
2026-04-24 6:32 ` Guixin Liu
2026-04-24 8:38 ` Andy Shevchenko [this message]
2026-04-30 2:01 ` Guixin Liu
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=aessHrL4jkCbSjNA@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=kanie@linux.alibaba.com \
--cc=linux-pci@vger.kernel.org \
--cc=oliver.yang@linux.alibaba.com \
--cc=xlpang@linux.alibaba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox