From: Stephen Boyd <sboyd@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Chris Paterson <chris.paterson2@renesas.com>,
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: Tue, 21 May 2019 11:01:36 -0700 [thread overview]
Message-ID: <20190521180137.A7A30217D7@mail.kernel.org> (raw)
In-Reply-To: <CAMuHMdVOKDRYjzmyRq-KXW8d+dYmAxnM+=y2yOh85YDcCEDMuw@mail.gmail.com>
Quoting Geert Uytterhoeven (2019-05-21 01:57:20)
> Hi Stephen, Andrew,
>
> On Thu, May 16, 2019 at 11:54 PM Stephen Boyd <sboyd@kernel.org> wrote:
> >
> > Guess so! Or Andrew does it.
>
> Given the change to scripts/spelling.txt conflicts with b937856a5db2cb7a
> ("scripts/spelling.txt: add more typos to spelling.txt and sort") in
> linux-next, and the risk of conflict with future changes to
> drivers/clk/renesas/r8a77470-cpg-mssr.c is slim, I'd like to defer this
> to Andrew.
>
> Acked-by: Geert Uytterhoeven <geert+renesas@glider.be>
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.
next prev parent reply other threads:[~2019-05-21 18:01 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 [this message]
2019-05-23 9:07 ` Chris Paterson
2019-05-23 18:06 ` Stephen Boyd
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=20190521180137.A7A30217D7@mail.kernel.org \
--to=sboyd@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=biju.das@bp.renesas.com \
--cc=chris.paterson2@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.