Linux PCI Non-Transparent Bridge framework and drivers
 help / color / mirror / Atom feed
From: Manivannan Sadhasivam <mani@kernel.org>
To: Koichiro Den <den@valinux.co.jp>
Cc: "Frank Li" <Frank.li@oss.nxp.com>,
	"Frank Li" <Frank.Li@kernel.org>,
	"Niklas Cassel" <cassel@kernel.org>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Jon Mason" <jdmason@kudzu.us>,
	"Dave Jiang" <dave.jiang@intel.com>,
	"Allen Hubbe" <allenbh@gmail.com>,
	"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
	"Kishon Vijay Abraham I" <kishon@kernel.org>,
	ntb@lists.linux.dev, linux-pci@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] PCI: endpoint: pci-epf-vntb: Honor MSI-X selection
Date: Thu, 15 Oct 2026 11:21:55 +0530	[thread overview]
Message-ID: <atBo0WvV9S2xhVc4@debian> (raw)
In-Reply-To: <j43nhj3wyu5tocjiots2xm4v2yxtngsxoaafkvxtputxxttw7j@snrzxkr66vkp>


[...]

> (+To: Mani)
> 
> BTW, I'm thinking of basing the next revision on [1] (thanks for the review
> there too). This MSI-X fix conflicts with it, and it's not just a textual
> conflict; the new link-event notification also needs to care about the MSI vs
> MSI-X selection.
> 
> Since [1] already has your Reviewed-by,

You mean Frank?

> I expect it to land in pci/endpoint
> first. Please let me know if you have any objections to adding [1] as a
> dependency.
> 

It mostly looks good to me. I'll apply it today so that you can send this patch
on top of pci/endpoint.

- Mani

-- 
மணிவண்ணன் சதாசிவம்

      reply	other threads:[~2026-10-15  5:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-14  5:32 [PATCH v4] PCI: endpoint: pci-epf-vntb: Honor MSI-X selection Koichiro Den
2026-10-14  5:48 ` sashiko-bot
2026-10-14 14:39 ` Frank Li
2026-10-14 15:06   ` Koichiro Den
2026-10-14 16:39     ` Koichiro Den
2026-10-15  5:51       ` Manivannan Sadhasivam [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=atBo0WvV9S2xhVc4@debian \
    --to=mani@kernel.org \
    --cc=Frank.Li@kernel.org \
    --cc=Frank.li@oss.nxp.com \
    --cc=allenbh@gmail.com \
    --cc=bhelgaas@google.com \
    --cc=cassel@kernel.org \
    --cc=dave.jiang@intel.com \
    --cc=den@valinux.co.jp \
    --cc=jdmason@kudzu.us \
    --cc=kishon@kernel.org \
    --cc=kwilczynski@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=ntb@lists.linux.dev \
    /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