[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3adf561b-2d6b-47be-8fca-2a26ee738670@kernel.org>
Date: Mon, 8 Apr 2024 07:37:22 +0200
From: Jiri Slaby <jirislaby@...nel.org>
To: Michael Ellerman <mpe@...erman.id.au>, Finn Thain
<fthain@...ux-m68k.org>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Andy Shevchenko <andy.shevchenko@...il.com>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
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 08. 04. 24, 7:32, Jiri Slaby wrote:
> On 08. 04. 24, 7:29, Michael Ellerman wrote:
>> Many maintainers won't drop Cc: tags if they are there in the submitted
>> patch. So I agree with Andy that we should encourage folks not to add
>> them in the first place.
>
> But fix the docs first.
>
> I am personally not biased to any variant (as in: I don't care where CCs
> live in a patch).
OTOH, as a submitter, it's a major PITA to carry CCs in notes (to have
those under the --- line). Esp. when I have patches in a queue for years.
How do people handle that? (Like rebases on current kernel.)
> regards,
--
js
suse labs
Powered by blists - more mailing lists