From: Stefan-gabriel Mirea <stefan-gabriel.mirea@nxp.com>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: "mark.rutland@arm.com" <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"corbet@lwn.net" <corbet@lwn.net>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Leo Li <leoyang.li@nxp.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
"jslaby@suse.com" <jslaby@suse.com>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"will@kernel.org" <will@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3 4/7] serial: fsl_linflexuart: Be consistent with the name
Date: Thu, 5 Sep 2019 11:32:06 +0000 [thread overview]
Message-ID: <VI1PR0402MB2863B0A0D1D12FA9CC2515E2DFBB0@VI1PR0402MB2863.eurprd04.prod.outlook.com> (raw)
In-Reply-To: 20190904075259.GA10983@kroah.com
Hello Greg,
On 9/4/2019 10:53 AM, gregkh@linuxfoundation.org wrote:
> On Fri, Aug 23, 2019 at 07:11:37PM +0000, Stefan-gabriel Mirea wrote:
>> For consistency reasons, spell the controller name as "LINFlexD" in
>> comments and documentation.
>>
>> Signed-off-by: Stefan-Gabriel Mirea <stefan-gabriel.mirea@nxp.com>
>> ---
>> Documentation/admin-guide/kernel-parameters.txt | 2 +-
>> drivers/tty/serial/Kconfig | 8 ++++----
>> drivers/tty/serial/fsl_linflexuart.c | 4 ++--
>> include/uapi/linux/serial_core.h | 4 ++--
>> 4 files changed, 9 insertions(+), 9 deletions(-)
>
> Doesn't apply to my tty-next tree :(
Thanks for letting me know; I will fix this in v4.
Regards,
Stefan
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-09-05 11:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-23 19:11 [PATCH v3 0/7] Add initial support for S32V234-EVB Stefan-gabriel Mirea
2019-08-23 19:11 ` [PATCH v3 1/7] dt-bindings: arm: fsl: Add the S32V234-EVB board Stefan-gabriel Mirea
2019-08-23 19:11 ` [PATCH v3 2/7] arm64: Introduce config for S32 Stefan-gabriel Mirea
2019-08-23 19:11 ` [PATCH v3 3/7] serial: fsl_linflexuart: Update compatible string Stefan-gabriel Mirea
2019-08-23 19:11 ` [PATCH v3 4/7] serial: fsl_linflexuart: Be consistent with the name Stefan-gabriel Mirea
2019-09-04 7:52 ` gregkh
2019-09-05 11:32 ` Stefan-gabriel Mirea [this message]
2019-08-23 19:11 ` [PATCH v3 5/7] arm64: dts: fsl: Add device tree for S32V234-EVB Stefan-gabriel Mirea
2019-08-23 19:11 ` [PATCH v3 6/7] dt-bindings: serial: Document Freescale LINFlexD UART Stefan-gabriel Mirea
2019-08-27 20:26 ` Rob Herring
2019-08-23 19:11 ` [PATCH v3 7/7] arm64: defconfig: Enable configs for S32V234 Stefan-gabriel Mirea
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=VI1PR0402MB2863B0A0D1D12FA9CC2515E2DFBB0@VI1PR0402MB2863.eurprd04.prod.outlook.com \
--to=stefan-gabriel.mirea@nxp.com \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
--cc=will@kernel.org \
/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).