From: Francesco Dolcini <francesco@dolcini.it>
To: David Lin <yu-hao.lin@nxp.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"briannorris@chromium.org" <briannorris@chromium.org>,
"kvalo@kernel.org" <kvalo@kernel.org>,
"francesco@dolcini.it" <francesco@dolcini.it>,
Sharvari Harisangam <sharvari.harisangam@nxp.com>,
Pete Hsieh <tsung-hsien.hsieh@nxp.com>
Subject: Re: [PATCH v6 0/6] wifi: mwifiex: added code to support host mlme.
Date: Fri, 20 Oct 2023 17:24:53 +0200 [thread overview]
Message-ID: <ZTKbxe1bAkfRI29V@francesco-nb.int.toradex.com> (raw)
In-Reply-To: <PA4PR04MB96388A628D6AB8359D3DAAD0D1DBA@PA4PR04MB9638.eurprd04.prod.outlook.com>
On Fri, Oct 20, 2023 at 03:48:06AM +0000, David Lin wrote:
> Patch v6:
> Correct mailing sequence.
You are still doing something wrong sending the patches over email, the
various emails are not threaded as expected, git-send-email should do
everything for you.
No need to re-send now IMO, but please figure out what's wrong for the
next time.
To give you an idea here [1] you see this email alone.
This [2] and this [3] are examples of a properly sent patch series (just random
series from your NXP colleagues).
You have also a winmail.dat file attached to every email in this series,
not sure what it is, but I would try to not send it.
Francesco
[1] https://lore.kernel.org/all/PA4PR04MB96388A628D6AB8359D3DAAD0D1DBA@PA4PR04MB9638.eurprd04.prod.outlook.com/
[2] https://lore.kernel.org/all/1697794232-2607-1-git-send-email-shengjiu.wang@nxp.com/
[3] https://lore.kernel.org/all/20230811101232.844769-1-neeraj.sanjaykale@nxp.com/
next prev parent reply other threads:[~2023-10-20 15:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 3:48 [PATCH v6 0/6] wifi: mwifiex: added code to support host mlme David Lin
2023-10-20 15:24 ` Francesco Dolcini [this message]
2023-10-23 2:11 ` [EXT] " David Lin
2023-10-23 9:07 ` Kalle Valo
2023-10-24 7:27 ` David Lin
2023-10-24 0:02 ` Jeff Johnson
2023-10-24 6:07 ` [EXT] " David Lin
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=ZTKbxe1bAkfRI29V@francesco-nb.int.toradex.com \
--to=francesco@dolcini.it \
--cc=briannorris@chromium.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=sharvari.harisangam@nxp.com \
--cc=tsung-hsien.hsieh@nxp.com \
--cc=yu-hao.lin@nxp.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;
as well as URLs for NNTP newsgroup(s).