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: Thu, 16 May 2019 14:54:05 -0700 [thread overview]
Message-ID: <20190516215406.75E5D2082E@mail.kernel.org> (raw)
In-Reply-To: <CAMuHMdWPSyrhYx5Z5mgmKrR68cHL6owcRT=B3+DD3GhhxuG4zw@mail.gmail.com>
Quoting Geert Uytterhoeven (2019-05-15 00:32:46)
> On Tue, May 14, 2019 at 11:19 PM Stephen Boyd <sboyd@kernel.org> wrote:
> > Quoting Chris Paterson (2019-05-14 08:33:41)
> > > Misspelling 'prohibited' is quite common in the real world, although
> > > surprisingly not so much in the Linux Kernel. In addition to fixing the
> > > typo we may as well add it to the spelling checker.
> > >
> > > Also adding the present participle (prohibiting).
> > >
> > > Fixes: 5bf2fbbef50c ("clk: renesas: cpg-mssr: Add r8a77470 support")
> > >
> > > Signed-off-by: Chris Paterson <chris.paterson2@renesas.com>
>
> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
>
> > Acked-by: Stephen Boyd <sboyd@kernel.org>
>
> Thanks!
>
> So I guess I'll queue this in clk-renesas-for-v5.3?
>
Guess so! Or Andrew does it.
next prev parent reply other threads:[~2019-05-16 21:54 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 [this message]
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
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=20190516215406.75E5D2082E@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 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).