Re: Build regressions/improvements in v5.16-rc1

From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Nick Terrell <terrelln@fb.com>
Cc: "Randy Dunlap" <rdunlap@infradead.org>,
	"Helge Deller" <deller@gmx.de>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Rob Clark" <robdclark@gmail.com>,
	"James E.J. Bottomley" <James.Bottomley@hansenpartnership.com>,
	"Anton Altaparmakov" <anton@tuxera.com>,
	"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
	"Sergio Paracuellos" <sergio.paracuellos@gmail.com>,
	"Herbert Xu" <herbert@gondor.apana.org.au>,
	"Joey Gouly" <joey.gouly@arm.com>,
	"Stan Skowronek" <stan@corellium.com>,
	"Hector Martin" <marcan@marcan.st>,
	"Andrey Ryabinin" <ryabinin.a.a@gmail.com>,
	"André Almeida" <andrealmeid@collabora.com>,
	"Peter Zijlstra" <peterz@infradead.org>,
	"Linux ARM" <linux-arm-kernel@lists.infradead.org>,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	"Parisc List" <linux-parisc@vger.kernel.org>,
	linux-arm-msm <linux-arm-msm@vger.kernel.org>,
	"DRI Development" <dri-devel@lists.freedesktop.org>,
	"linux-ntfs-dev@lists.sourceforge.net"
	<linux-ntfs-dev@lists.sourceforge.net>,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	"open list:BROADCOM NVRAM DRIVER" <linux-mips@vger.kernel.org>,
	linux-pci <linux-pci@vger.kernel.org>,
	"Linux Crypto Mailing List" <linux-crypto@vger.kernel.org>,
	kasan-dev <kasan-dev@googlegroups.com>
Subject: Re: Build regressions/improvements in v5.16-rc1
Date: Wed, 17 Nov 2021 09:24:12 +0100	[thread overview]
Message-ID: <CAMuHMdWgGz5FSidaGpp8YRRSnJfwdP4-wOkXdVx+mydXnMAXHQ@mail.gmail.com> (raw)
In-Reply-To: <B57193D6-1FD4-45D3-8045-8D2DE691E24E@fb.com>

Hi Nick,

On Wed, Nov 17, 2021 at 3:20 AM Nick Terrell <terrelln@fb.com> wrote:
> > On Nov 16, 2021, at 6:05 PM, Randy Dunlap <rdunlap@infradead.org> wrote:
> > On 11/16/21 5:59 PM, Nick Terrell wrote:
> >> I’ll send the PR to Linus tomorrow. I’ve been informed that it
> >> isn't strictly necessary to send the patches to the mailing list
> >> for bug fixes, but its already done, so I’ll wait and see if there
> >> is any feedback.
> >
> > IMO several (or many more) people would disagree with that.
> >
> > "strictly?"  OK, it's probably possible that almost any patch
> > could be merged without being on a mailing list, but it's not
> > desirable (except in the case of "security" patches).
>
> Good to know! Thanks for the advice, I wasn’t really sure what
> the best practice is for sending patches to your own tree, as I
> didn't see anything about it in the maintainer guide.

All patches must be sent to public mailing lists for review.
You might get away with not doing that for a simple and trivial fix,
but be prepared to end up on people's "special" lists if you did get
it wrong.

We are Legion. We do not forgive. We do not forget ;-)

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