[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5dd285bd-b9a8-c85c-9bd9-a839c10e78fd@linux-m68k.org>
Date: Fri, 5 Apr 2024 09:17:27 +1100 (AEDT)
From: Finn Thain <fthain@...ux-m68k.org>
To: Andy Shevchenko <andy.shevchenko@...il.com>
cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jiri Slaby <jirislaby@...nel.org>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Michael Ellerman <mpe@...erman.id.au>, Nicholas Piggin <npiggin@...il.com>,
Christophe Leroy <christophe.leroy@...roup.eu>,
"Aneesh Kumar K.V" <aneesh.kumar@...nel.org>,
"Naveen N. Rao" <naveen.n.rao@...ux.ibm.com>,
linux-m68k@...ts.linux-m68k.org, linux-kernel@...r.kernel.org,
linux-serial@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org
Subject: Re: [PATCH] serial/pmac_zilog: Remove flawed mitigation for rx irq
flood
On Thu, 4 Apr 2024, Andy Shevchenko wrote:
>
> > > > ---
> > > (here is a good location for Cc:)
> >
> > Documentation/process/submitting-patches.rst indicats that it should
> > be above the "---" separator together with Acked-by etc. Has this
> > convention changed recently?
>
> I see, I will prepare a patch to discuss this aspect.
>
If you are going to veto patches on the basis of rules yet unwritten, I
think you risk turning the kernel development process into a lottery.
How many other patches presently under review will need to be dropped just
in case they don't conform with possible future rules?
Powered by blists - more mailing lists