[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAMuHMdV2WAnhFWJFEGOqch4h8mQ31w459ejOmn=39KWj1wAXsQ@mail.gmail.com>
Date: Fri, 28 Oct 2022 15:04:42 +0200
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Bagas Sanjaya <bagasdotme@...il.com>
Cc: linux-m68k@...ts.linux-m68k.org, linux-kernel@...r.kernel.org,
Michael Schmitz <schmitzmic@...il.com>
Subject: Re: [PATCH] m68k: mac: Reword comment using double "in"
Hi Bagas,
On Fri, Oct 28, 2022 at 3:01 PM Bagas Sanjaya <bagasdotme@...il.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@...il.com>
> > Signed-off-by: Geert Uytterhoeven <geert@...ux-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@...il.com>
Thanks!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-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
Powered by blists - more mailing lists