From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org,
Michael Schmitz <schmitzmic@gmail.com>
Subject: Re: [PATCH] m68k: mac: Reword comment using double "in"
Date: Fri, 28 Oct 2022 15:04:42 +0200 [thread overview]
Message-ID: <CAMuHMdV2WAnhFWJFEGOqch4h8mQ31w459ejOmn=39KWj1wAXsQ@mail.gmail.com> (raw)
In-Reply-To: <Y1vSjQfkDfPINUBo@debian.me>
Hi Bagas,
On Fri, Oct 28, 2022 at 3:01 PM Bagas Sanjaya <bagasdotme@gmail.com> wrote:
> On Fri, Oct 28, 2022 at 10:30:26AM +0200, Geert Uytterhoeven wrote:
> > People keep on sending (incorrect) patches to remove the second
> > occurrence of the word "in". Reword the comment to stop the inflood.
>
> Ah! People who aren't fluent in English think that duplicated "in" below
> isn't OK, which after stripping that become nonsense without reading the
> actual code.
>
> > Suggested-by: Michael Schmitz <schmitzmic@gmail.com>
> > Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
> > ---
> > To be queued in the m68k branch for v6.2.
>
> Should this patch be Cc: stable'ed so that no more trivial patches as
> you mentioned?
People should not be sending patches against stable in the first place.
Once this makes it upstream, the inflow should stop (hopefully ;-)
> Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>
Thanks!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2022-10-28 13:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 8:30 [PATCH] m68k: mac: Reword comment using double "in" Geert Uytterhoeven
2022-10-28 13:01 ` Bagas Sanjaya
2022-10-28 13:04 ` Geert Uytterhoeven [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='CAMuHMdV2WAnhFWJFEGOqch4h8mQ31w459ejOmn=39KWj1wAXsQ@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=bagasdotme@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=schmitzmic@gmail.com \
/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).