Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Darshit Shah <darnshah@amazon.de>
Cc: bhelgaas@google.com, Jonthan.Cameron@huawei.com, darnir@gnu.org,
	lukas@wunner.de, feng.tang@linux.alibaba.com, kbusch@kernel.org,
	kwilczynski@kernel.org, linux-kernel@vger.kernel.org,
	linux-pci@vger.kernel.org, olof@lixom.net,
	sathyanarayanan.kuppuswamy@linux.intel.com
Subject: Re: [PATCH v3 RESEND] drivers/pci: Decouple DPC from AER service
Date: Mon, 22 Jun 2026 12:03:29 -0500	[thread overview]
Message-ID: <20260622170329.GA675275@bhelgaas> (raw)
In-Reply-To: <ai8h-wyXz8l30X-V@dev-dsk-darnshah-1c-a4c7d5e9.eu-west-1.amazon.com>

On Sun, Jun 14, 2026 at 09:54:17PM +0000, Darshit Shah wrote:
> Hi Bjorn,
> Can you please pick this patch up in the PCI tree for the next version?
> Anything I can do to help expedite the process?

Sorry, I missed this and I don't want to add new changes right now
since we're halfway through the v7.2 merge window.  Can you ping again
after v7.2-rc1, and we can make it v7.3 material?

  reply	other threads:[~2026-06-22 17:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-28 12:20 [PATCH] drivers/pci: Allow attaching AER to non-RP devices that support MSI Darshit Shah
2025-11-28 17:07 ` Lukas Wunner
2025-12-08 11:25   ` [PATCH v2 0/1] " Darshit Shah
2025-12-08 11:25     ` [PATCH v2 1/1] drivers/pci: Decouple DPC from AER service Darshit Shah
2025-12-09  7:45       ` Lukas Wunner
2025-12-11 16:42         ` [PATCH v3] " Darshit Shah
2026-02-28 23:59           ` Darshit Shah
2026-06-14 21:54           ` [PATCH v3 RESEND] " Darshit Shah
2026-06-22 17:03             ` Bjorn Helgaas [this message]
2026-07-09  7:52               ` Darshit Shah
2026-07-10 17:00           ` [PATCH v3] " Bjorn Helgaas
2025-12-09 15:29       ` [PATCH v2 1/1] " Sathyanarayanan Kuppuswamy
2025-12-09  0:30 ` [PATCH] drivers/pci: Allow attaching AER to non-RP devices that support MSI Bjorn Helgaas

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=20260622170329.GA675275@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=Jonthan.Cameron@huawei.com \
    --cc=bhelgaas@google.com \
    --cc=darnir@gnu.org \
    --cc=darnshah@amazon.de \
    --cc=feng.tang@linux.alibaba.com \
    --cc=kbusch@kernel.org \
    --cc=kwilczynski@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=olof@lixom.net \
    --cc=sathyanarayanan.kuppuswamy@linux.intel.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