From: Manivannan Sadhasivam <mani@kernel.org>
To: "Jon Mason" <jdmason@kudzu.us>,
"Dave Jiang" <dave.jiang@intel.com>,
"Allen Hubbe" <allenbh@gmail.com>,
"Kishon Vijay Abraham I" <kishon@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Frank Li" <Frank.Li@nxp.com>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"Jerome Brunet" <jbrunet@baylibre.com>
Cc: ntb@lists.linux.dev, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] PCI: endpoint: pci-epf-vntb: allow arbitrary BAR mapping
Date: Mon, 23 Jun 2025 06:06:46 -0600 [thread overview]
Message-ID: <175068040623.12516.4425064763865712731.b4-ty@kernel.org> (raw)
In-Reply-To: <20250603-pci-vntb-bar-mapping-v2-0-fc685a22ad28@baylibre.com>
On Tue, 03 Jun 2025 19:03:37 +0200, Jerome Brunet wrote:
> The patchset allows arbitrary BAR mapping for vNTB PCI endpoint function.
>
> This was developed for the Renesas platform with requires a mapping that
> was not possible before:
> * BAR0 (1MB): CTRL+SPAD
> * BAR2 (1MB): MW0
> * BAR4 (256B): Doorbell
>
> [...]
Applied, thanks!
[1/3] PCI: endpoint: pci-epf-vntb: Return an error code on bar init
commit: 7ea488cce73263231662e426639dd3e836537068
[2/3] PCI: endpoint: pci-epf-vntb: Align mw naming with config names
commit: a079d83c4afd4896f7f29bd9e807cb382043b360
[3/3] PCI: endpoint: pci-epf-vntb: Allow BAR assignment via configfs
commit: a0cc6e6fd072616315147ac68a12672d5a2fa223
Best regards,
--
Manivannan Sadhasivam <mani@kernel.org>
prev parent reply other threads:[~2025-06-23 12:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-03 17:03 Jerome Brunet
2025-06-03 17:03 ` [PATCH v2 1/3] PCI: endpoint: pci-epf-vntb: Return an error code on bar init Jerome Brunet
2025-06-03 17:03 ` [PATCH v2 2/3] PCI: endpoint: pci-epf-vntb: Align mw naming with config names Jerome Brunet
2025-06-03 19:43 ` Frank Li
2025-06-03 17:03 ` [PATCH v2 3/3] PCI: endpoint: pci-epf-vntb: Allow BAR assignment via configfs Jerome Brunet
2025-06-03 19:46 ` Frank Li
2025-06-30 20:38 ` Bjorn Helgaas
2025-07-01 7:37 ` Jerome Brunet
2025-06-23 12:06 ` 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=175068040623.12516.4425064763865712731.b4-ty@kernel.org \
--to=mani@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=allenbh@gmail.com \
--cc=bhelgaas@google.com \
--cc=dave.jiang@intel.com \
--cc=jbrunet@baylibre.com \
--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
all inboxes | Powered by JetHome®