From: Dave Jiang <dave.jiang@intel.com>
To: Koichiro Den <den@valinux.co.jp>, Jon Mason <jdmason@kudzu.us>
Cc: Allen Hubbe <allenbh@gmail.com>, Frank Li <Frank.Li@nxp.com>,
Niklas Cassel <cassel@kernel.org>,
ntb@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] NTB: Allow drivers to provide DMA mapping device
Date: Thu, 5 Mar 2026 09:32:47 -0700 [thread overview]
Message-ID: <17cdfa38-16d5-49cc-ac61-20b606a4308b@intel.com> (raw)
In-Reply-To: <lwayvep2vqwplyc45nr45zcz7rawutxe6q637p6gagw6asmlu3@ohqlnlmoymwl>
On 3/4/26 8:23 PM, Koichiro Den wrote:
> On Wed, Mar 04, 2026 at 09:53:42AM -0700, Dave Jiang wrote:
<snip>
>> Probably should include it with this series if it's small. Having the user with new code is usually preferred.
>
> I thought that, since the vNTB patch wouldn't work until the NTB changes are in,
> asking both the NTB and PCI EP maintainers to coordinate the apply order might
> be a bit awkward.
>
> That said, if preferable, I can include the vNTB change in this series and
> explicitly ask the PCI EP maintainers not to pick up (new) Patch 3 until the NTB
> maintainers have acked and applied Patch 1-2.
Given that most of the patches are PCI EP, I think with acks from NTB, the whole thing can go through PCI EP if that works for you.
DJ
>
> I'd also appreciate any thoughts from Jon or others on this (i.e. keeping
> this series NTB tree-only vs. including the vNTB change as well), as well
> as any feedback on this v1 series itself.
>
> P.S. I sent a corrected code snippet a few minutes after my original post. The
> original snippet above was wrong, as it would violate the kernel-doc in Patch 1:
>
> "Drivers that implement .get_dma_dev() must return a non-NULL pointer."
>
> Best regards,
> Koichiro
>
>>
prev parent reply other threads:[~2026-03-05 16:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 14:45 [PATCH 0/2] NTB: Allow drivers to provide DMA mapping device Koichiro Den
2026-03-02 14:45 ` [PATCH 1/2] NTB: core: Add .get_dma_dev() callback to ntb_dev_ops Koichiro Den
2026-03-02 14:45 ` [PATCH 2/2] NTB: ntb_transport: Use ntb_get_dma_dev() for DMA buffers Koichiro Den
2026-03-02 16:52 ` [PATCH 0/2] NTB: Allow drivers to provide DMA mapping device Dave Jiang
2026-03-03 4:56 ` Koichiro Den
2026-03-03 15:42 ` Dave Jiang
2026-03-04 15:56 ` Koichiro Den
2026-03-04 16:03 ` Koichiro Den
2026-03-04 16:53 ` Dave Jiang
2026-03-05 3:23 ` Koichiro Den
2026-03-05 16:32 ` Dave Jiang [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=17cdfa38-16d5-49cc-ac61-20b606a4308b@intel.com \
--to=dave.jiang@intel.com \
--cc=Frank.Li@nxp.com \
--cc=allenbh@gmail.com \
--cc=cassel@kernel.org \
--cc=den@valinux.co.jp \
--cc=jdmason@kudzu.us \
--cc=linux-kernel@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