From: Stefan-gabriel Mirea <stefan-gabriel.mirea@nxp.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "corbet@lwn.net" <corbet@lwn.net>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"will@kernel.org" <will@kernel.org>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
Leo Li <leoyang.li@nxp.com>, "jslaby@suse.com" <jslaby@suse.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v6 3/5] serial: fsl_linflexuart: Be consistent with the name
Date: Wed, 16 Oct 2019 11:01:57 +0000 [thread overview]
Message-ID: <VI1PR0402MB2863EC2DF6464234DE4E0A16DF920@VI1PR0402MB2863.eurprd04.prod.outlook.com> (raw)
In-Reply-To: 20191015190155.GA1140159@kroah.com
Hello Greg,
On 10/15/2019 10:05 PM, Greg KH wrote:
>
> This patch does not apply to my tree :(
>
Thanks for letting me know; I will rebase it in v7.
Regards,
Stefan
next prev parent reply other threads:[~2019-10-16 11:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 16:52 [PATCH v6 0/5] Add initial support for S32V234-EVB Stefan-Gabriel Mirea
2019-10-10 16:52 ` [PATCH v6 1/5] dt-bindings: arm: fsl: Add the S32V234-EVB board Stefan-Gabriel Mirea
2019-10-10 16:52 ` [PATCH v6 2/5] arm64: Introduce config for S32 Stefan-Gabriel Mirea
2019-10-10 16:52 ` [PATCH v6 3/5] serial: fsl_linflexuart: Be consistent with the name Stefan-Gabriel Mirea
2019-10-15 19:01 ` Greg KH
2019-10-16 11:01 ` Stefan-gabriel Mirea [this message]
2019-10-10 16:52 ` [PATCH v6 4/5] arm64: dts: fsl: Add device tree for S32V234-EVB Stefan-Gabriel Mirea
2019-10-10 16:52 ` [PATCH v6 5/5] 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=VI1PR0402MB2863EC2DF6464234DE4E0A16DF920@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).