Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Shawn Lin <shawn.lin@rock-chips.com>
To: Niklas Cassel <cassel@kernel.org>
Cc: shawn.lin@rock-chips.com, Bjorn Helgaas <bhelgaas@google.com>,
	Manivannan Sadhasivam <mani@kernel.org>,
	linux-rockchip@lists.infradead.org, linux-pci@vger.kernel.org,
	Peter Geis <pgwipeout@gmail.com>
Subject: Re: [PATCH 0/2] Two small INTx fixes for Rockchip's dwc based PCIe controller driver
Date: Thu, 3 Sep 2026 16:26:50 +0800	[thread overview]
Message-ID: <aa7c0d0b-7522-40e4-9249-4cf220fce3b7@rock-chips.com> (raw)
In-Reply-To: <apktsxxgZ3yFclo0@ryzen>

在 2026/09/03 星期四 16:20, Niklas Cassel 写道:
> Hello Shawn,
> 
> On Thu, Sep 03, 2026 at 10:44:35AM +0800, Shawn Lin wrote:
>>
>> This small series fixes two INTx related issues in the Rockchip
>> DesignWare PCIe controller driver.
>>
>> Note that patch 2 depends on b376b3ff9cb0 which is not yet in Linus'
>> tree, so this series is based on linux-next.
> 
> $ git tag --contains b376b3ff9cb0
> v7.3-rc1
> 
> FWIW, the commit you are referencing is in Linus' tree already.

Ah, a few days ago I didn't send out the patch in time, but now it is 
indeed on Linus' tree.

Thanks.

> 
> 
> Kind regards,
> Niklas
> 


      reply	other threads:[~2026-09-03  9:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-03  2:44 [PATCH 0/2] Two small INTx fixes for Rockchip's dwc based PCIe controller driver Shawn Lin
2026-09-03  2:44 ` [PATCH 1/2] PCI: dw-rockchip: Bail out if the INTx irq domain creation fails Shawn Lin
2026-09-03  3:12   ` sashiko-bot
2026-09-03  3:42     ` Shawn Lin
2026-09-03  2:44 ` [PATCH 2/2] PCI: dw-rockchip: Do not recreate the INTx irq domain on root port reset Shawn Lin
2026-09-03  3:13   ` sashiko-bot
2026-09-03  3:46     ` Shawn Lin
2026-09-03  8:37   ` Niklas Cassel
2026-09-03 10:02     ` Shawn Lin
2026-09-03  8:20 ` [PATCH 0/2] Two small INTx fixes for Rockchip's dwc based PCIe controller driver Niklas Cassel
2026-09-03  8:26   ` Shawn Lin [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=aa7c0d0b-7522-40e4-9249-4cf220fce3b7@rock-chips.com \
    --to=shawn.lin@rock-chips.com \
    --cc=bhelgaas@google.com \
    --cc=cassel@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=mani@kernel.org \
    --cc=pgwipeout@gmail.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