From: Christoph Hellwig <hch@lst.de>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>
Cc: Christoph Hellwig <hch@lst.de>,
"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
mpe@ellerman.id.au, paul.walmsley@sifive.com, palmer@dabbelt.com,
Rob Herring <robh+dt@kernel.org>,
m.szyprowski@samsung.com, Robin Murphy <robin.murphy@arm.com>,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH v3 0/4] Use dma_default_coherent for devicetree default coherency
Date: Tue, 28 Mar 2023 03:18:12 +0200 [thread overview]
Message-ID: <20230328011812.GA21977@lst.de> (raw)
In-Reply-To: <CB41D3AF-20F6-42F3-9168-C0D6E716431A@flygoat.com>
On Fri, Mar 24, 2023 at 09:17:38AM +0000, Jiaxun Yang wrote:
> >
> > 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.
Ok. I'll really need review from the MIPS and drivers/of/ maintainers,
through.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>
Cc: Christoph Hellwig <hch@lst.de>,
"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
mpe@ellerman.id.au, paul.walmsley@sifive.com, palmer@dabbelt.com,
Rob Herring <robh+dt@kernel.org>,
m.szyprowski@samsung.com, Robin Murphy <robin.murphy@arm.com>,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH v3 0/4] Use dma_default_coherent for devicetree default coherency
Date: Tue, 28 Mar 2023 03:18:12 +0200 [thread overview]
Message-ID: <20230328011812.GA21977@lst.de> (raw)
In-Reply-To: <CB41D3AF-20F6-42F3-9168-C0D6E716431A@flygoat.com>
On Fri, Mar 24, 2023 at 09:17:38AM +0000, Jiaxun Yang wrote:
> >
> > 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.
Ok. I'll really need review from the MIPS and drivers/of/ maintainers,
through.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
linux-kernel@vger.kernel.org,
"linux-mips@vger.kernel.org" <linux-mips@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,
Christoph Hellwig <hch@lst.de>,
m.szyprowski@samsung.com
Subject: Re: [PATCH v3 0/4] Use dma_default_coherent for devicetree default coherency
Date: Tue, 28 Mar 2023 03:18:12 +0200 [thread overview]
Message-ID: <20230328011812.GA21977@lst.de> (raw)
In-Reply-To: <CB41D3AF-20F6-42F3-9168-C0D6E716431A@flygoat.com>
On Fri, Mar 24, 2023 at 09:17:38AM +0000, Jiaxun Yang wrote:
> >
> > 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.
Ok. I'll really need review from the MIPS and drivers/of/ maintainers,
through.
next prev parent reply other threads:[~2023-03-28 1:18 UTC|newest]
Thread overview: 45+ 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 ` Jiaxun Yang
2023-03-21 11:08 ` Jiaxun Yang
2023-03-21 11:08 ` [PATCH v3 1/4] of: address: Fix default coherency for MIPS Jiaxun Yang
2023-03-21 11:08 ` Jiaxun Yang
2023-03-21 11:08 ` Jiaxun Yang
2023-03-28 14:15 ` Rob Herring
2023-03-28 14:15 ` Rob Herring
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 ` Jiaxun Yang
2023-03-21 11:08 ` 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 ` Jiaxun Yang
2023-03-21 11:08 ` 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-21 11:08 ` Jiaxun Yang
2023-03-21 11:08 ` Jiaxun Yang
2023-03-28 14:17 ` Rob Herring
2023-03-28 14:17 ` Rob Herring
2023-03-28 14:17 ` Rob Herring
2023-03-29 3:27 ` Michael Ellerman
2023-03-29 3:27 ` Michael Ellerman
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 7:29 ` Christoph Hellwig
2023-03-23 7:29 ` Christoph Hellwig
2023-03-23 21:07 ` Jiaxun Yang
2023-03-23 21:07 ` Jiaxun Yang
2023-03-23 21:07 ` Jiaxun Yang
2023-03-23 21:39 ` Christoph Hellwig
2023-03-23 21:39 ` Christoph Hellwig
2023-03-23 21:39 ` Christoph Hellwig
2023-03-24 9:17 ` Jiaxun Yang
2023-03-24 9:17 ` Jiaxun Yang
2023-03-24 9:17 ` Jiaxun Yang
2023-03-28 1:18 ` Christoph Hellwig [this message]
2023-03-28 1:18 ` Christoph Hellwig
2023-03-28 1:18 ` Christoph Hellwig
2023-03-28 7:45 ` Thomas Bogendoerfer
2023-03-28 7:45 ` Thomas Bogendoerfer
2023-03-28 7:45 ` Thomas Bogendoerfer
2023-03-28 13:02 ` Jiaxun Yang
2023-03-28 13:02 ` Jiaxun Yang
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=20230328011812.GA21977@lst.de \
--to=hch@lst.de \
--cc=jiaxun.yang@flygoat.com \
--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=mpe@ellerman.id.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.