From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: linux-serial <linux-serial@vger.kernel.org>
Cc: "Greg KH" <gregkh@linuxfoundation.org>,
"Jiri Slaby" <jirislaby@kernel.org>,
"Neil Armstrong" <narmstrong@baylibre.com>,
"Kevin Hilman" <khilman@baylibre.com>,
"Jerome Brunet" <jbrunet@baylibre.com>,
"Martin Blumenstingl" <martin.blumenstingl@googlemail.com>,
"Andreas Färber" <afaerber@suse.de>,
"Manivannan Sadhasivam" <mani@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org,
linux-actions@lists.infradead.org,
linux-unisoc@lists.infradead.org
Subject: Re: [PATCH 5/6] cleanup: Use UART_XMIT_SIZE
Date: Mon, 20 Jun 2022 13:39:52 +0300 (EEST) [thread overview]
Message-ID: <aa117e1a-7ec-149b-2337-db4ead968aa@linux.intel.com> (raw)
In-Reply-To: <20220620103408.37454-6-ilpo.jarvinen@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 428 bytes --]
On Mon, 20 Jun 2022, Ilpo Järvinen wrote:
> Both UART_XMIT_SIZE and SERIAL_XMIT_SIZE are defined. Make them all
> UART_XMIT_SIZE.
>
> Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
Grr, it seems that my internal naming to organize patches managed to leak
into that summary on subject line. It should have been serial: obviously
and I only noticed while git send-email was sending the bits out. :-(
--
i.
[-- Attachment #2: Type: text/plain, Size: 167 bytes --]
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
prev parent reply other threads:[~2022-06-20 10:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220620103408.37454-1-ilpo.jarvinen@linux.intel.com>
2022-06-20 10:34 ` [PATCH 5/6] cleanup: Use UART_XMIT_SIZE Ilpo Järvinen
2022-06-20 10: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=aa117e1a-7ec-149b-2337-db4ead968aa@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=afaerber@suse.de \
--cc=gregkh@linuxfoundation.org \
--cc=jbrunet@baylibre.com \
--cc=jirislaby@kernel.org \
--cc=khilman@baylibre.com \
--cc=linux-actions@lists.infradead.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-unisoc@lists.infradead.org \
--cc=mani@kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=narmstrong@baylibre.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).