From: Bjorn Helgaas <helgaas@kernel.org>
To: Frank Li <Frank.li@oss.nxp.com>
Cc: "Manivannan Sadhasivam" <mani@kernel.org>,
"Jeff Hugo" <jeff.hugo@oss.qualcomm.com>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Kishon Vijay Abraham I" <kishon@kernel.org>,
"Frank Li" <Frank.Li@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Koichiro Den" <den@valinux.co.jp>,
"Niklas Cassel" <cassel@kernel.org>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Christian Bruel" <christian.bruel@foss.st.com>,
"open list:MHI BUS" <mhi@lists.linux.dev>,
"open list:MHI BUS" <linux-arm-msm@vger.kernel.org>,
"open list:PCI ENDPOINT SUBSYSTEM" <linux-pci@vger.kernel.org>,
"open list" <linux-kernel@vger.kernel.org>,
imx@lists.linux.dev, "Frank Li" <Frank.Li@nxp.com>
Subject: Re: [PATCH v2 1/1] PCI: Replace chan->device->dev with dmaengine_get_provider_device()
Date: Thu, 5 Nov 2026 15:38:47 -0600 [thread overview]
Message-ID: <20261105213847.GA1565775@bhelgaas> (raw)
In-Reply-To: <auz2EAk-b-ZsX6PW@SMW015318>
On Thu, Nov 05, 2026 at 03:33:04PM -0600, Frank Li wrote:
> On Wed, Nov 04, 2026 at 03:27:10PM -0600, Bjorn Helgaas wrote:
> > On Wed, Nov 04, 2026 at 10:01:59AM -0500, Frank.Li@oss.nxp.com wrote:
> > > From: Frank Li <Frank.Li@nxp.com>
> > >
> > > Use the dmaengine_get_provider_device() API instead of directly
> > > accessing chan->device->dev to get the DMA provider device.
> > >
> > > No functional change. Prepare make to struct dma_device private to the DMA
> > > engine.
> >
> > "Prepare to make ..." I assume?
>
> Yes, Do you need me respin it or you can fix when apply?
I'm sure Mani can fix it.
prev parent reply other threads:[~2026-11-05 21:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 15:01 Frank.Li
2026-11-04 20:46 ` Andy Shevchenko
2026-11-04 21:27 ` Bjorn Helgaas
2026-11-05 21:33 ` Frank Li
2026-11-05 21:38 ` Bjorn Helgaas [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=20261105213847.GA1565775@bhelgaas \
--to=helgaas@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=Frank.li@oss.nxp.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=cassel@kernel.org \
--cc=christian.bruel@foss.st.com \
--cc=den@valinux.co.jp \
--cc=imx@lists.linux.dev \
--cc=jeff.hugo@oss.qualcomm.com \
--cc=kishon@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mani@kernel.org \
--cc=mhi@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®