From: Jakub Kicinski <kuba@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Johannes Berg <johannes@sipsolutions.net>,
Benjamin Berg <benjamin.berg@intel.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH net 09/12] wifi: mac80211: fix kernel-doc notation warning
Date: Tue, 11 Jul 2023 20:37:02 -0700 [thread overview]
Message-ID: <20230711203702.001235a4@kernel.org> (raw)
In-Reply-To: <20230710230312.31197-10-rdunlap@infradead.org>
On Mon, 10 Jul 2023 16:03:09 -0700 Randy Dunlap wrote:
> + * @agg: station's active links data
That does not sound right. It'd be better to wait for the WiFi
maintainers to return to get the WiFi bits merged. Can we defer
WiFi patches for now?
next prev parent reply other threads:[~2023-07-12 3:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 23:03 [PATCH net 00/12] net: fix kernel-doc problems in include/net/ Randy Dunlap
2023-07-10 23:03 ` [PATCH net 01/12] net: bonding: remove kernel-doc comment marker Randy Dunlap
2023-07-10 23:03 ` [PATCH net 02/12] wifi: cfg80211: remove dead/unused enum value Randy Dunlap
2023-07-10 23:03 ` [PATCH net 03/12] net: cfg802154: fix kernel-doc notation warnings Randy Dunlap
2023-07-11 8:36 ` Miquel Raynal
2023-07-10 23:03 ` [PATCH net 04/12] codel: " Randy Dunlap
2023-07-10 23:03 ` [PATCH net 05/12] devlink: " Randy Dunlap
2023-07-10 23:03 ` [PATCH net 06/12] wifi: radiotap: " Randy Dunlap
2023-07-10 23:03 ` [PATCH net 07/12] inet: frags: remove kernel-doc comment marker Randy Dunlap
2023-07-12 3:34 ` Jakub Kicinski
2023-07-12 3:48 ` Randy Dunlap
2023-07-10 23:03 ` [PATCH net 08/12] net: llc: fix kernel-doc notation warnings Randy Dunlap
2023-07-10 23:03 ` [PATCH net 09/12] wifi: mac80211: fix kernel-doc notation warning Randy Dunlap
2023-07-12 3:37 ` Jakub Kicinski [this message]
2023-07-12 3:46 ` Randy Dunlap
2023-07-10 23:03 ` [PATCH net 10/12] net: NSH: " Randy Dunlap
2023-07-10 23:03 ` [PATCH net 11/12] pie: " Randy Dunlap
2023-07-10 23:03 ` [PATCH net 12/12] rsi: remove kernel-doc comment marker Randy Dunlap
2023-07-11 8:58 ` Kalle Valo
2023-07-12 3:37 ` Jakub Kicinski
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=20230711203702.001235a4@kernel.org \
--to=kuba@kernel.org \
--cc=benjamin.berg@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rdunlap@infradead.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).