From: Jeff Johnson <quic_jjohnson@quicinc.com>
To: Shiji Yang <yangshiji66@outlook.com>, <linux-wireless@vger.kernel.org>
Cc: Stanislaw Gruszka <stf_xl@wp.pl>, Kalle Valo <kvalo@kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/3] wifi: rt2x00: improve watchdog support
Date: Mon, 6 Nov 2023 08:33:39 -0800 [thread overview]
Message-ID: <ec7d829b-28c3-400b-97f9-e6d2f5a4d4aa@quicinc.com> (raw)
In-Reply-To: <TYAP286MB0315D63EBE1DE458D6B9D42ABCA4A@TYAP286MB0315.JPNP286.PROD.OUTLOOK.COM>
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@TYAP286MB0315.JPNP286.PROD.OUTLOOK.COM>
X-Microsoft-Original-Message-ID:
<20231104085800.17576-1-yangshiji66@outlook.com>
Subject: [PATCH v2 1/3] wifi: rt2x00: introduce DMA busy check watchdog
for rt2800
Message-ID:
<TYAP286MB0315D7462CE08A119A99DE34BCA4A@TYAP286MB0315.JPNP286.PROD.OUTLOOK.COM>
In-Reply-To: <20231104085800.17576-1-yangshiji66@outlook.com>
References: <20231104085800.17576-1-yangshiji66@outlook.com>
Subject: [PATCH v2 2/3] wifi: rt2x00: disable RTS threshold for rt2800
by default
Message-ID:
<TYAP286MB03155DDB953155B7A2DE849ABCA4A@TYAP286MB0315.JPNP286.PROD.OUTLOOK.COM>
In-Reply-To: <20231104085800.17576-1-yangshiji66@outlook.com>
References: <20231104085800.17576-1-yangshiji66@outlook.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.
prev parent reply other threads:[~2023-11-06 16:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-04 8:57 Shiji Yang
2023-11-06 16:33 ` Jeff Johnson [this message]
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=ec7d829b-28c3-400b-97f9-e6d2f5a4d4aa@quicinc.com \
--to=quic_jjohnson@quicinc.com \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=stf_xl@wp.pl \
--cc=yangshiji66@outlook.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
all inboxes | Powered by JetHome®