From: Jiaxun Yang <jiaxun.yang@flygoat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
palmer@dabbelt.com, paul.walmsley@sifive.com,
Robin Murphy <robin.murphy@arm.com>,
linux-riscv@lists.infradead.org, linuxppc-dev@lists.ozlabs.org,
m.szyprowski@samsung.com
Subject: Re: [PATCH v3 0/4] Use dma_default_coherent for devicetree default coherency
Date: Fri, 24 Mar 2023 09:17:38 +0000 [thread overview]
Message-ID: <CB41D3AF-20F6-42F3-9168-C0D6E716431A@flygoat.com> (raw)
In-Reply-To: <20230323213930.GA7730@lst.de>
> 2023年3月23日 21:39，Christoph Hellwig <hch@lst.de> 写道：
>
> On Thu, Mar 23, 2023 at 09:07:31PM +0000, Jiaxun Yang wrote:
>>
>>
>>> 2023年3月23日 07:29，Christoph Hellwig <hch@lst.de> 写道：
>>>
>>> The series looks fine to me. How should we merge it?
>>
>> Perhaps go through dma-mapping tree?
>
> Is patch a 6.3 candidate or should all of it go into 6.4?
Please leave it for 6.4, as corresponding MIPS arch part will be a part of 6.4.
Thanks
Jiaxun
next prev parent reply other threads:[~2023-03-24 9:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 11:08 [PATCH v3 0/4] Use dma_default_coherent for devicetree default coherency Jiaxun Yang
2023-03-21 11:08 ` [PATCH v3 1/4] of: address: Fix default coherency for MIPS Jiaxun Yang
2023-03-28 14:15 ` Rob Herring
2023-03-21 11:08 ` [PATCH v3 2/4] dma-mapping: Provide a fallback dma_default_coherent Jiaxun Yang
2023-03-21 11:08 ` [PATCH v3 3/4] dma-mapping: Provide CONFIG_ARCH_DMA_DEFAULT_COHERENT Jiaxun Yang
2023-03-21 11:08 ` [PATCH v3 4/4] of: address: Always use dma_default_coherent for default coherency Jiaxun Yang
2023-03-28 14:17 ` Rob Herring
2023-03-29 3:27 ` Michael Ellerman
2023-03-23 7:29 ` [PATCH v3 0/4] Use dma_default_coherent for devicetree " Christoph Hellwig
2023-03-23 21:07 ` Jiaxun Yang
2023-03-23 21:39 ` Christoph Hellwig
2023-03-24 9:17 ` Jiaxun Yang [this message]
2023-03-28 1:18 ` Christoph Hellwig
2023-03-28 7:45 ` Thomas Bogendoerfer
2023-03-28 13:02 ` Jiaxun Yang
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=CB41D3AF-20F6-42F3-9168-C0D6E716431A@flygoat.com \
--to=jiaxun.yang@flygoat.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=m.szyprowski@samsung.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--cc=tsbogend@alpha.franken.de \
/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;
as well as URLs for NNTP newsgroup(s).