From: Jiri Slaby <jirislaby@kernel.org>
To: Michael Ellerman <mpe@ellerman.id.au>,
Finn Thain <fthain@linux-m68k.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org,
"Aneesh Kumar K.V" <aneesh.kumar@kernel.org>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Nicholas Piggin <npiggin@gmail.com>,
linux-serial@vger.kernel.org,
"Naveen N. Rao" <naveen.n.rao@linux.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] serial/pmac_zilog: Remove flawed mitigation for rx irq flood
Date: Mon, 8 Apr 2024 07:32:53 +0200 [thread overview]
Message-ID: <b1553164-18db-4f5c-b1a5-28a393d64941@kernel.org> (raw)
In-Reply-To: <87v84sbexv.fsf@mail.lhotse>
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).
regards,
--
js
suse labs
next prev parent reply other threads:[~2024-04-08 5:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 4:11 [PATCH] serial/pmac_zilog: Remove flawed mitigation for rx irq flood Finn Thain
2024-04-03 22:29 ` Andy Shevchenko
2024-04-03 23:59 ` Finn Thain
2024-04-04 9:24 ` Andy Shevchenko
2024-04-04 22:17 ` Finn Thain
2024-04-05 5:05 ` Andy Shevchenko
2024-04-05 3:06 ` Michael Ellerman
2024-04-05 3:46 ` Finn Thain
2024-04-08 5:29 ` Michael Ellerman
2024-04-08 5:32 ` Jiri Slaby [this message]
2024-04-08 5:37 ` Jiri Slaby
2024-04-08 5:44 ` Greg Kroah-Hartman
2024-04-08 8:32 ` Geert Uytterhoeven
2024-04-05 5:09 ` Andy Shevchenko
2024-04-04 5:07 ` Jiri Slaby
2024-04-04 9:20 ` Andy Shevchenko
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=b1553164-18db-4f5c-b1a5-28a393d64941@kernel.org \
--to=jirislaby@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=aneesh.kumar@kernel.org \
--cc=fthain@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-serial@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=naveen.n.rao@linux.ibm.com \
--cc=npiggin@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