From: Krzysztof Kozlowski <krzk@kernel.org>
To: Biju Das <biju.das.jz@bp.renesas.com>,
Borislav Petkov <bp@alien8.de>,
"biju.das.au" <biju.das.au@gmail.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
Kiryl Shutsemau <kas@kernel.org>,
Rick Edgecombe <rick.p.edgecombe@intel.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
"linux-coco@lists.linux.dev" <linux-coco@lists.linux.dev>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Au Dang <au.dang.jx@renesas.com>
Subject: Re: [PATCH v3 0/4] Fix transmit handling on SCI/RSCI ports
Date: Tue, 27 Oct 2026 08:23:36 +0100 [thread overview]
Message-ID: <072dd88c-4ca1-4c8a-98b1-7783bc43c1c5@kernel.org> (raw)
In-Reply-To: <TY3PR01MB113468FBD8E5EFA65C4B4E5EB86602@TY3PR01MB11346.jpnprd01.prod.outlook.com>
On 27/10/2026 08:19, Biju Das wrote:
> Hi Borislav Petkov,
>
> Thanks for the feedback.
>
>> -----Original Message-----
>> From: Borislav Petkov <bp@alien8.de>
>> Sent: 27 October 2026 05:58
>> Subject: Re: [PATCH v3 0/4] Fix transmit handling on SCI/RSCI ports
>>
>> On Mon, Oct 26, 2026 at 11:23:32AM +0000, Biju Das wrote:
>>> drivers/tty/serial/rsci.c | 4 ++-
>>> drivers/tty/serial/sh-sci-common.h | 4 +++
>>> drivers/tty/serial/sh-sci.c | 71 ++++++++++++++++++++++++++------------
>>> 3 files changed, 56 insertions(+), 23 deletions(-)
>>
>> $ ./scripts/get_maintainer.pl --no-rolestats -f drivers/tty/serial/rsci.c drivers/tty/serial/sh-sci-
>> common.h drivers/tty/serial/sh-sci.c Greg Kroah-Hartman <gregkh@linuxfoundation.org> Jiri Slaby
>> <jirislaby@kernel.org> Biju Das <biju.das.jz@bp.renesas.com> Geert Uytterhoeven <geert+renesas@glider.be>
>> Hugo Villeneuve <hvilleneuve@dimonoff.com> Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
>> Frank Li <Frank.Li@nxp.com>
>> linux-kernel@vger.kernel.org
>> linux-serial@vger.kernel.org
>>
>> So why is
>>
>> x86@kernel.org, linux-coco@lists.linux.dev
>>
>> in your Cc: list?
>>
>> What can those people do about Renesas-something-serial driver?
>
> I have been told by some maintainers to use b4 for easy review
> rather than using 'git send-mail'.
>
> If I do 'b4 prep --auto-to-cc' as per the b4 documentation,
> x86@kernel.org is automatically listed.
After 'b4 prep --auto-to-cc' you edit the cover letter and see what is
there, no? You can easily spot bogus addressed added.
>
> Can you please guide me how to remove x86@kernel.org from b4 tooling
> So that x86@kernel.org will not automatically listed?
b4 does not add these addresses for these files.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-10-27 7:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 11:23 [PATCH v3 0/4] Fix transmit handling on SCI/RSCI ports Biju Das
2026-10-26 11:23 ` [PATCH v3 1/4] serial: sh-sci: Drop TE disable at end of transmission on SCI Biju Das
2026-10-26 11:53 ` sashiko-bot
2026-10-26 11:23 ` [PATCH v3 2/4] serial: sh-sci: Keep TX enabled on TEI while data is pending Biju Das
2026-10-26 12:13 ` sashiko-bot
2026-10-26 11:23 ` [PATCH v3 3/4] serial: sh-sci: Skip TDxE clear when hardware clears it automatically Biju Das
2026-10-26 11:52 ` sashiko-bot
2026-10-26 11:23 ` [PATCH v3 4/4] serial: sh-sci: Toggle TE when restoring SCSCR in console write on SCI Biju Das
2026-10-26 11:54 ` sashiko-bot
2026-10-27 5:57 ` [PATCH v3 0/4] Fix transmit handling on SCI/RSCI ports Borislav Petkov
2026-10-27 7:19 ` Biju Das
2026-10-27 7:23 ` Krzysztof Kozlowski [this message]
2026-10-27 8:33 ` Biju Das
2026-10-27 9:34 ` Krzysztof Kozlowski
2026-10-27 20:54 ` Borislav Petkov
2026-10-28 9:13 ` Biju Das
2026-10-28 11:02 ` Krzysztof Kozlowski
2026-10-28 15:47 ` Borislav Petkov
2026-10-30 2:33 ` [PATCH] MAINTAINERS: Fix Intel TDX kernel file patterns Borislav Petkov
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=072dd88c-4ca1-4c8a-98b1-7783bc43c1c5@kernel.org \
--to=krzk@kernel.org \
--cc=au.dang.jx@renesas.com \
--cc=biju.das.au@gmail.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=kas@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=rick.p.edgecombe@intel.com \
--cc=x86@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.