From: Shawn Guo <shawnguo@kernel.org>
To: Stephen Boyd <sboyd@kernel.org>
Cc: Leonard Crestez <leonard.crestez@nxp.com>,
Michael Turquette <mturquette@baylibre.com>,
Aisheng Dong <aisheng.dong@nxp.com>,
Fabio Estevam <fabio.estevam@nxp.com>,
Jacky Bai <ping.bai@nxp.com>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
dl-linux-imx <linux-imx@nxp.com>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] clk: imx6sll: Fix mispelling uart4_serial as serail
Date: Sun, 12 May 2019 09:07:42 +0800 [thread overview]
Message-ID: <20190512010741.GI15856@dragon> (raw)
In-Reply-To: <155750984356.14659.16650159344577092731@swboyd.mtv.corp.google.com>
On Fri, May 10, 2019 at 10:37:23AM -0700, Stephen Boyd wrote:
> Quoting Shawn Guo (2019-05-09 20:27:47)
> > On Tue, Apr 23, 2019 at 07:05:08PM +0000, Leonard Crestez wrote:
> > > This looks like a copy-paste error. This string is not referenced
> > > anywhere so it's safe to rename it.
> > >
> > > Signed-off-by: Leonard Crestez <leonard.crestez@nxp.com>
> >
> > I see this keep coming, so have to ask you to fix your patch sender.
> > The base64 encoding makes it very difficult to apply patch. I have done
> > manual applying for your patches a couple of times, and I thought that's
> > just accident. It seems not. Please fix and resend.
> >
>
> I already applied this one. Sorry, forgot to send the email.
No problem. Thanks for notification.
Shawn
prev parent reply other threads:[~2019-05-12 1:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 19:05 [PATCH] clk: imx6sll: Fix mispelling uart4_serial as serail Leonard Crestez
2019-05-10 3:27 ` Shawn Guo
2019-05-10 17:37 ` Stephen Boyd
2019-05-12 1:07 ` Shawn Guo [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=20190512010741.GI15856@dragon \
--to=shawnguo@kernel.org \
--cc=aisheng.dong@nxp.com \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=leonard.crestez@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=mturquette@baylibre.com \
--cc=ping.bai@nxp.com \
--cc=sboyd@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).