From: Frank Li <Frank.li@nxp.com>
To: Lorenzo Pieralisi <lpieralisi@kernel.org>
Cc: hch@infradead.org, bhelgaas@google.com,
christophe.jaillet@wanadoo.fr, imx@lists.linux.dev, kw@linux.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, minghuan.Lian@nxp.com,
mingkai.hu@nxp.com, robh@kernel.org, roy.zang@nxp.com
Subject: Re: [PATCH v3 1/1] PCI: layerscape-ep: set 64-bit DMA mask
Date: Tue, 10 Oct 2023 12:02:56 -0400 [thread overview]
Message-ID: <ZSV1sINV/2GrAYFr@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <169695244699.95067.12901655371819245761.b4-ty@kernel.org>
On Tue, Oct 10, 2023 at 05:44:23PM +0200, Lorenzo Pieralisi wrote:
> On Tue, 26 Sep 2023 10:04:45 -0400, Frank Li wrote:
> > Set DMA mask and coherent DMA mask to enable 64-bit addressing.
> >
> >
>
> Read this:
> https://lore.kernel.org/linux-pci/20171026223701.GA25649@bhelgaas-glaptop.roam.corp.google.com
>
> Find the issue with the commit log (that I fixed).
Do you means "set" should be "Set"?
Frank
>
> This does not apply to v6.6-rc1 so I tweaked it,
> check that everything is OK please.
>
> Applied to controller/layerscape, thanks!
Thanks, everthing is good!
>
> [1/1] PCI: layerscape-ep: set 64-bit DMA mask
> https://git.kernel.org/pci/pci/c/81ef01bc5934
>
> Thanks,
> Lorenzo
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-10-10 16:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 14:04 [PATCH v3 1/1] PCI: layerscape-ep: set 64-bit DMA mask Frank Li
2023-09-27 9:26 ` Christoph Hellwig
2023-09-27 12:46 ` Manivannan Sadhasivam
2023-10-10 14:18 ` Frank Li
2023-09-27 13:25 ` Roy Zang
2023-10-10 15:44 ` Lorenzo Pieralisi
2023-10-10 16:02 ` Frank Li [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=ZSV1sINV/2GrAYFr@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=bhelgaas@google.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=hch@infradead.org \
--cc=imx@lists.linux.dev \
--cc=kw@linux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lpieralisi@kernel.org \
--cc=minghuan.Lian@nxp.com \
--cc=mingkai.hu@nxp.com \
--cc=robh@kernel.org \
--cc=roy.zang@nxp.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