From: Jakub Kicinski <kuba@kernel.org>
To: Kalle Valo <kvalo@kernel.org>
Cc: "Breno Leitao" <leitao@debian.org>,
davem@davemloft.net, pabeni@redhat.com, edumazet@google.com,
dsahern@kernel.org, weiwan@google.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, horms@kernel.org, andrew@lunn.ch,
leit@fb.com, "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Kees Cook" <keescook@chromium.org>,
"Johannes Berg" <johannes.berg@intel.com>,
"Emmanuel Grumbach" <emmanuel.grumbach@intel.com>,
"Justin Stitt" <justinstitt@google.com>,
"Li Zetao" <lizetao1@huawei.com>,
"Francois Romieu" <romieu@fr.zoreil.com>,
"Rob Herring" <robh@kernel.org>,
"Marc Kleine-Budde" <mkl@pengutronix.de>,
"Ruan Jinjie" <ruanjinjie@huawei.com>,
linux-wireless@vger.kernel.org (open list:TI WILINK WIRELESS
DRIVERS)
Subject: Re: [PATCH net 1/9] wifi: fill in MODULE_DESCRIPTION()s for wlcore
Date: Tue, 30 Jan 2024 18:14:35 -0800 [thread overview]
Message-ID: <20240130181435.13f6e2cc@kernel.org> (raw)
In-Reply-To: <170662101207.2289851.7564186430529596261.kvalo@kernel.org>
On Tue, 30 Jan 2024 13:23:34 +0000 (UTC) Kalle Valo wrote:
> > W=1 builds now warn if module is built without a MODULE_DESCRIPTION().
> > Add descriptions to the TI WLAN wlcore drivers.
> >
> > Signed-off-by: Breno Leitao <leitao@debian.org>
>
> These patches go to wireless-next, not net. But no need to resend because of this.
FWIW I've been taking these thru net (or wireless in your case)
rather than the -next tree. There's zero chance of regression
here and the warnings are annoying. But up to you.
--
pw-bot: au
next prev parent reply other threads:[~2024-01-31 2:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 10:42 [PATCH net 0/9] wifi: Fix MODULE_DESCRIPTION() for net (p4) Breno Leitao
2024-01-30 10:42 ` Breno Leitao
2024-01-30 10:42 ` [PATCH net 1/9] wifi: fill in MODULE_DESCRIPTION()s for wlcore Breno Leitao
2024-01-30 13:23 ` Kalle Valo
2024-01-31 2:14 ` Jakub Kicinski [this message]
2024-01-31 5:10 ` Kalle Valo
2024-01-31 16:33 ` Kalle Valo
2024-01-30 10:42 ` [PATCH net 2/9] wifi: fill in MODULE_DESCRIPTION()s for wl1251 and wl12xx Breno Leitao
2024-01-30 10:42 ` [PATCH net 3/9] wifi: fill in MODULE_DESCRIPTION()s for Broadcom WLAN Breno Leitao
2024-01-30 10:42 ` [PATCH net 4/9] wifi: fill in MODULE_DESCRIPTION()s for ar5523 Breno Leitao
2024-01-30 10:42 ` [PATCH net 5/9] wifi: fill in MODULE_DESCRIPTION()s for wcn36xx Breno Leitao
2024-01-30 17:29 ` Jeff Johnson
2024-01-30 10:42 ` [PATCH net 6/9] wifi: fill in MODULE_DESCRIPTION()s for p54spi Breno Leitao
2024-02-01 14:54 ` Christian Lamparter
2024-01-30 10:42 ` [PATCH net 7/9] wifi: fill in MODULE_DESCRIPTION()s for wl18xx Breno Leitao
2024-01-30 10:42 ` [PATCH net 8/9] wifi: fill in MODULE_DESCRIPTION()s for wilc1000 Breno Leitao
2024-01-30 10:42 ` [PATCH net 9/9] wifi: fill in MODULE_DESCRIPTION()s for mt76 drivers Breno Leitao
2024-01-30 10:42 ` Breno Leitao
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=20240130181435.13f6e2cc@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=emmanuel.grumbach@intel.com \
--cc=horms@kernel.org \
--cc=johannes.berg@intel.com \
--cc=justinstitt@google.com \
--cc=keescook@chromium.org \
--cc=kvalo@kernel.org \
--cc=leit@fb.com \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lizetao1@huawei.com \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
--cc=romieu@fr.zoreil.com \
--cc=ruanjinjie@huawei.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=weiwan@google.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.