From: Kalle Valo <kvalo@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, sfr@canb.auug.org.au,
lkp@intel.com
Subject: Re: [PATCH wireless] MAINTAINERS: add common wireless and wireless-next trees
Date: Fri, 14 Jan 2022 19:23:10 +0200 [thread overview]
Message-ID: <87tue6s03l.fsf@kernel.org> (raw)
In-Reply-To: <20220114081932.475eaf86@kicinski-fedora-PC1C0HJN.hsd1.ca.comcast.net> (Jakub Kicinski's message of "Fri, 14 Jan 2022 08:19:32 -0800")
Jakub Kicinski <kuba@kernel.org> writes:
> On Fri, 14 Jan 2022 15:34:15 +0200 Kalle Valo wrote:
>> +Q: http://patchwork.kernel.org/project/linux-wireless/list/
>
> nit: https?
Good point, I'll add that. I'll also change the existing links to use
https.
While looking at MAINTAINERS file more, I found this odd small entry in
the MAINTAINERS file:
NETWORKING [WIRELESS]
L: linux-wireless@vger.kernel.org
Q: http://patchwork.kernel.org/project/linux-wireless/list/
It seems to be an artifact from this commit:
0e324cf640fb MAINTAINERS: changes for wireless
I don't see how that section is needed so I'll remove that as well.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2022-01-14 17:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 13:34 [PATCH wireless] MAINTAINERS: add common wireless and wireless-next trees Kalle Valo
2022-01-14 16:19 ` Jakub Kicinski
2022-01-14 17:23 ` Kalle Valo [this message]
2022-01-14 21:18 ` Stephen Rothwell
2022-01-15 11:11 ` Kalle Valo
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=87tue6s03l.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.