From: Kalle Valo <kvalo@kernel.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Jakub Kicinski <kuba@kernel.org>,
davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH net] MAINTAINERS: exclude wireless drivers from netdev
Date: Fri, 12 May 2023 07:06:15 +0300 [thread overview]
Message-ID: <87y1lumbwo.fsf@kernel.org> (raw)
In-Reply-To: <d505bf5bbcd0f13a37f9c8465667e355ce20bc26.camel@sipsolutions.net> (Johannes Berg's message of "Thu, 11 May 2023 18:38:37 +0200")
Johannes Berg <johannes@sipsolutions.net> writes:
> On Thu, 2023-05-11 at 09:03 -0700, Jakub Kicinski wrote:
>> It seems that we mostly get netdev CCed on wireless patches
>> which are written by people who don't know any better and
>> CC everything that get_maintainers spits out. Rather than
>> patches which indeed could benefit from general networking
>> review.
>>
>> Marking them down in patchwork as Awaiting Upstream is
>> a bit tedious.
>>
>> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
>> ---
>> CC: kvalo@kernel.org
>> CC: johannes@sipsolutions.net
>> CC: linux-wireless@vger.kernel.org
>>
>> Is this okay with everyone?
>>
>
> Yeah, makes sense.
>
> Acked-by: Johannes Berg <johannes@sipsolutions.net>
I didn't even know about 'X', a very good idea:
Acked-by: Kalle Valo <kvalo@kernel.org>
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2023-05-12 4:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 16:03 [PATCH net] MAINTAINERS: exclude wireless drivers from netdev Jakub Kicinski
2023-05-11 16:38 ` Johannes Berg
2023-05-12 4:06 ` Kalle Valo [this message]
2023-05-11 16:50 ` Marcel Holtmann
2023-05-11 23:45 ` Jakub Kicinski
2023-05-12 8:00 ` patchwork-bot+netdevbpf
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=87y1lumbwo.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 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.