From: Kalle Valo <kvalo@qca.qualcomm.com>
To: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Switching away from ath10k patchwork project
Date: Wed, 5 Jul 2017 13:29:20 +0000 [thread overview]
Message-ID: <87tw2rgggu.fsf@kamboji.qca.qualcomm.com> (raw)
TL;DR:
Starting from patches submitted today I'm switching away from
ath10k specific patchwork project to the general linux-wireless
patchwork project.
The longer story:
For legacy reasons we have had two patchwork projects, the main project
being linux-wireless (which tracks linux-wireless mailing list):
https://patchwork.kernel.org/project/linux-wireless/list/?state=3D*
And then we have a separate project for ath10k (which tracks the ath10k
mailing list):
https://patchwork.kernel.org/project/ath10k/list/?state=3D*
This creates a confusion as people don't always know which patchwork
project to follow. To simplify this I'm dropping the ath10k project in
patchwork and track also ath10k patches using the general linux-wireless
project so that all wireless patches can be tracked from the same
patchwork project.
The only downside from this is that if someone posts a patch only to the
ath10k list and forgets to CC linux-wireless I will not see it as I only
take patches from patchwork. But we have instructed everyone to CC
linux-wireless anyway[1] so hopefully this is a small problem. I do
remember having few cases where the patch was not CCed to
linux-wireless, but usually it's actually the other way around (people
forget to CC the ath10k list). So I'm not expecting that much problems
with this change.
[1] https://wireless.wiki.kernel.org/en/users/drivers/ath10k/submittingpatc=
hes
--=20
Kalle Valo=
reply other threads:[~2017-07-05 13:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87tw2rgggu.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.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 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).