linux-kernel - Re: [PATCH v2 0/3] wifi: rt2x00: improve watchdog support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <ec7d829b-28c3-400b-97f9-e6d2f5a4d4aa@quicinc.com>
Date:   Mon, 6 Nov 2023 08:33:39 -0800
From:   Jeff Johnson <quic_jjohnson@...cinc.com>
To:     Shiji Yang <yangshiji66@...look.com>,
        <linux-wireless@...r.kernel.org>
CC:     Stanislaw Gruszka <stf_xl@...pl>, Kalle Valo <kvalo@...nel.org>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 0/3] wifi: rt2x00: improve watchdog support

On 11/4/2023 1:57 AM, Shiji Yang wrote:
> P.S. It seems that this cover letter won't be included in the patch
> series in https://lore.kernel.org/. It's an issue with the Outlook
> email or I missed something?

Outlook e-mail is apparently rewriting your e-mail headers:

Subject: [PATCH v2 0/3] wifi: rt2x00: improve watchdog support
Message-ID: 
<TYAP286MB0315D63EBE1DE458D6B9D42ABCA4A@...P286MB0315.JPNP286.PROD.OUTLOOK.COM>
X-Microsoft-Original-Message-ID: 
<20231104085800.17576-1-yangshiji66@...look.com>

Subject: [PATCH v2 1/3] wifi: rt2x00: introduce DMA busy check watchdog 
for rt2800
Message-ID: 
<TYAP286MB0315D7462CE08A119A99DE34BCA4A@...P286MB0315.JPNP286.PROD.OUTLOOK.COM>
In-Reply-To: <20231104085800.17576-1-yangshiji66@...look.com>
References: <20231104085800.17576-1-yangshiji66@...look.com>

Subject: [PATCH v2 2/3] wifi: rt2x00: disable RTS threshold for rt2800 
by default
Message-ID: 
<TYAP286MB03155DDB953155B7A2DE849ABCA4A@...P286MB0315.JPNP286.PROD.OUTLOOK.COM>
In-Reply-To: <20231104085800.17576-1-yangshiji66@...look.com>
References: <20231104085800.17576-1-yangshiji66@...look.com>

Your actual patches are being threaded since they all reference the same 
Message ID, but the cover letter no longer has that Message ID.

You might want to look at using b4 
(<https://b4.docs.kernel.org/en/latest/contributor/overview.html>) 
instead of git send-email.

 From the linked page:
The main benefit of b4 send is that you no longer have to really care if 
your mail server performs some kind of content mangling that causes 
patches to become corrupted, or if it doesn’t provide a way to send mail 
via SMTP.