From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
linux-renesas-soc@vger.kernel.org,
linux-serial <linux-serial@vger.kernel.org>,
Milan Stevanovic <milan.stevanovic@se.com>,
Jimmy Lalande <jimmy.lalande@se.com>,
Pascal Eberhard <pascal.eberhard@se.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Herve Codina <herve.codina@bootlin.com>,
Clement Leger <clement.leger@bootlin.com>
Subject: Re: [PATCH v4 0/9] serial: 8250: dw: RZN1 DMA support
Date: Mon, 4 Apr 2022 17:39:38 +0300 (EEST) [thread overview]
Message-ID: <42b8671b-48a2-43f0-975b-3b9e98202328@linux.intel.com> (raw)
In-Reply-To: <20220404162050.7831ebfe@xps13>
On Mon, 4 Apr 2022, Miquel Raynal wrote:
> Hello,
>
> andriy.shevchenko@linux.intel.com wrote on Wed, 30 Mar 2022 17:13:16
> +0300:
>
> > On Wed, Mar 30, 2022 at 03:20:29PM +0200, Miquel Raynal wrote:
> > > Hello,
> > >
> > > Support for the RZN1 DMA engine allows us adapt a little bit the 8250 DW
> > > UART driver with to bring DMA support for this SoC.
> > >
> > > This short series applies on top of the series bringing RZN1 DMA
> > > support, currently on its v5, see [1]. Technically speaking, only the DT
> > > patch needs to be applied after [1]. The other patches can come in at
> > > any moment, because if no "dmas" property is provided in the DT, DMA
> > > support will simply be ignored.
> > >
> > > [1] https://lore.kernel.org/dmaengine/20220315191255.221473-1-miquel.raynal@bootlin.com/T/#m0ef3323abce3eec961e142bf2fb35e95b9045fc5
> >
> > Couple of versions ago I have asked you to Cc the series to Ilpo (Cc'ed).
> > I hope you will not forget it in v5.
>
> Sorry I forgot to re-add manually Ilpo in the recipients.
>
> Anyway, if Ilpo really needs to be Cc'ed, then there is something to do
> on MAINTAINER's side.
While I'm considering doing like you suggest, I don't think it can be in
general said that people who you're specificially told to Cc would be ok
to get dropped unless they're among the listed maintainers.
--
i.
prev parent reply other threads:[~2022-04-04 14:43 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 13:20 [PATCH v4 0/9] serial: 8250: dw: RZN1 DMA support Miquel Raynal
2022-03-30 13:20 ` [PATCH v4 1/9] serial: 8250: dw: Move definitions to the shared header Miquel Raynal
2022-03-30 14:08 ` Andy Shevchenko
2022-03-30 13:20 ` [PATCH v4 2/9] serial: 8250: dw: Use the device API Miquel Raynal
2022-03-30 13:58 ` Andy Shevchenko
2022-03-30 13:20 ` [PATCH v4 3/9] serial: 8250: dw: Create a more generic platform data structure Miquel Raynal
2022-03-30 14:02 ` Andy Shevchenko
2022-03-30 14:04 ` Andy Shevchenko
2022-03-30 13:20 ` [PATCH v4 4/9] serial: 8250: dw: Allow to use a fallback CPR value if not synthesized Miquel Raynal
2022-03-30 14:11 ` Andy Shevchenko
2022-03-30 13:20 ` [PATCH v4 5/9] serial: 8250: dma: Allow driver operations before starting DMA transfers Miquel Raynal
2022-03-30 14:07 ` Andy Shevchenko
2022-03-30 13:20 ` [PATCH v4 6/9] serial: 8250: dw: Introduce an rx_timeout variable in the IRQ path Miquel Raynal
2022-03-30 14:14 ` Andy Shevchenko
2022-03-30 13:20 ` [PATCH v4 7/9] serial: 8250: dw: Add support for DMA flow controlling devices Miquel Raynal
2022-03-30 14:16 ` Andy Shevchenko
2022-03-30 14:18 ` Andy Shevchenko
2022-04-01 10:56 ` Ilpo Järvinen
2022-04-01 17:38 ` Andy Shevchenko
2022-04-04 15:20 ` Miquel Raynal
2022-04-04 15:29 ` Ilpo Järvinen
2022-03-30 13:20 ` [PATCH v4 8/9] serial: 8250: dw: Improve RZN1 support Miquel Raynal
2022-03-30 14:19 ` Andy Shevchenko
2022-03-30 13:20 ` [PATCH v4 9/9] ARM: dts: r9a06g032: Fill the UART DMA properties Miquel Raynal
2022-03-30 14:13 ` [PATCH v4 0/9] serial: 8250: dw: RZN1 DMA support Andy Shevchenko
2022-04-04 14:20 ` Miquel Raynal
2022-04-04 14:39 ` Ilpo Järvinen [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=42b8671b-48a2-43f0-975b-3b9e98202328@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=clement.leger@bootlin.com \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=herve.codina@bootlin.com \
--cc=jimmy.lalande@se.com \
--cc=jirislaby@kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=milan.stevanovic@se.com \
--cc=miquel.raynal@bootlin.com \
--cc=pascal.eberhard@se.com \
--cc=thomas.petazzoni@bootlin.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;
as well as URLs for NNTP newsgroup(s).