From: Johannes Berg <johannes@sipsolutions.net>
To: Maoyi Xie <maoyixie.tju@gmail.com>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] wifi: nl80211: require CAP_NET_ADMIN over the target netns in SET_WIPHY_NETNS
Date: Tue, 05 May 2026 12:00:02 +0200 [thread overview]
Message-ID: <4a80d9a16c37af6f35904b5298238f64f030c374.camel@sipsolutions.net> (raw)
In-Reply-To: <20260504135420.1178443-2-maoyi.xie@ntu.edu.sg>
On Mon, 2026-05-04 at 21:54 +0800, Maoyi Xie wrote:
[...]
> Reported-by: Maoyi Xie <maoyi.xie@ntu.edu.sg>
Crediting yourself with finding the bug seems ... a bit weird?
But anyway
> Signed-off-by: Maoyi Xie <maoyi.xie@ntu.edu.sg>
Bot reports
WARNING: From:/Signed-off-by: email address mismatch: 'From: Maoyi Xie <maoyixie.tju@gmail.com>' != 'Signed-off-by: Maoyi Xie <maoyi.xie@ntu.edu.sg>'
so wonder if that was intentional? Maybe you wanted to include another
From: line?
johannes
next prev parent reply other threads:[~2026-05-05 10:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-04 12:57 [PATCH 0/2] wifi: nl80211: tighten netns handling in SET_WIPHY_NETNS and dump continuation Maoyi Xie
2026-05-04 12:57 ` [PATCH 1/2] wifi: nl80211: require CAP_NET_ADMIN over the target netns in SET_WIPHY_NETNS Maoyi Xie
2026-05-04 12:57 ` [PATCH 2/2] wifi: nl80211: re-check wiphy netns in nl80211_prepare_wdev_dump() continuation Maoyi Xie
2026-05-04 13:02 ` Johannes Berg
2026-05-04 13:54 ` [PATCH v2 0/2] wifi: nl80211: tighten netns handling in SET_WIPHY_NETNS and dump continuation Maoyi Xie
2026-05-04 13:54 ` [PATCH v2 1/2] wifi: nl80211: require CAP_NET_ADMIN over the target netns in SET_WIPHY_NETNS Maoyi Xie
2026-05-05 10:00 ` Johannes Berg [this message]
2026-05-06 6:27 ` Maoyi Xie
2026-05-04 13:54 ` [PATCH v2 2/2] wifi: nl80211: re-check wiphy netns in nl80211_prepare_wdev_dump() continuation Maoyi Xie
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=4a80d9a16c37af6f35904b5298238f64f030c374.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=maoyixie.tju@gmail.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