From: Stephen Boyd <sboyd@kernel.org>
To: Chris Paterson <Chris.Paterson2@renesas.com>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Biju Das <biju.das@bp.renesas.com>,
linux-clk <linux-clk@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] scripts/spelling.txt: Add spelling fix for prohibited
Date: Thu, 23 May 2019 11:06:01 -0700 [thread overview]
Message-ID: <20190523180602.4F1392075B@mail.kernel.org> (raw)
In-Reply-To: <TYAPR01MB2285F1CD8540CBC4795D8708B7010@TYAPR01MB2285.jpnprd01.prod.outlook.com>
Quoting Chris Paterson (2019-05-23 02:07:51)
> > From: Stephen Boyd <sboyd@kernel.org>
> >
> > Ok. Or Chris can split the patch into the clk part and the scripts/
> > part? They're only loosely related to each other, so I'm not sure why
> > they were sent in one patch besides for ease of transport.
>
> Happy to split the patch if you want. I combined the patch as I saw that done in a couple of examples in the git log.
>
> However, I got an automated email from akpm saying that this patch was added to the -mm tree; so I don't know if you still want me to split up this patch or not.
> Let me know.
>
Everything still looks fine to me so I dont' think you need to do
anything.
prev parent reply other threads:[~2019-05-23 18:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 15:33 [PATCH] scripts/spelling.txt: Add spelling fix for prohibited Chris Paterson
2019-05-14 21:19 ` Stephen Boyd
2019-05-15 7:32 ` Geert Uytterhoeven
2019-05-16 21:54 ` Stephen Boyd
2019-05-21 8:57 ` Geert Uytterhoeven
2019-05-21 18:01 ` Stephen Boyd
2019-05-23 9:07 ` Chris Paterson
2019-05-23 18:06 ` Stephen Boyd [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=20190523180602.4F1392075B@mail.kernel.org \
--to=sboyd@kernel.org \
--cc=Chris.Paterson2@renesas.com \
--cc=akpm@linux-foundation.org \
--cc=biju.das@bp.renesas.com \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.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).