From: patchwork-bot+bluetooth@kernel.org
To: Breno Leitao <leitao@debian.org>
Cc: kuba@kernel.org, davem@davemloft.net, pabeni@redhat.com,
edumazet@google.com, alex.aring@gmail.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
horms@kernel.org, andrew@lunn.ch,
linux-bluetooth@vger.kernel.org, linux-wpan@vger.kernel.org
Subject: Re: [PATCH net v2 4/9] net: fill in MODULE_DESCRIPTION()s for 6LoWPAN
Date: Wed, 28 Feb 2024 15:44:12 +0000 [thread overview]
Message-ID: <170913505272.28471.5112906084108672664.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240207101929.484681-5-leitao@debian.org>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 7 Feb 2024 02:19:23 -0800 you wrote:
> W=1 builds now warn if module is built without a MODULE_DESCRIPTION().
> Add descriptions to IPv6 over Low power Wireless Personal Area Network.
>
> Signed-off-by: Breno Leitao <leitao@debian.org>
> ---
> net/6lowpan/core.c | 1 +
> 1 file changed, 1 insertion(+)
Here is the summary with links:
- [net,v2,4/9] net: fill in MODULE_DESCRIPTION()s for 6LoWPAN
https://git.kernel.org/bluetooth/bluetooth-next/c/2898f3075e6a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-02-28 15:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 10:19 [PATCH net v2 0/9] net: Fix MODULE_DESCRIPTION() for net (p5) Breno Leitao
2024-02-07 10:19 ` [PATCH net v2 1/9] net: fill in MODULE_DESCRIPTION()s for xfrm Breno Leitao
2024-02-07 11:41 ` Simon Horman
2024-02-07 10:19 ` [PATCH net v2 2/9] net: fill in MODULE_DESCRIPTION()s for mpoa Breno Leitao
2024-02-07 11:41 ` Simon Horman
2024-02-07 10:19 ` [PATCH net v2 3/9] net: fill in MODULE_DESCRIPTION()s for af_key Breno Leitao
2024-02-07 11:41 ` Simon Horman
2024-02-07 10:19 ` [PATCH net v2 4/9] net: fill in MODULE_DESCRIPTION()s for 6LoWPAN Breno Leitao
2024-02-07 11:41 ` Simon Horman
2024-02-28 15:44 ` patchwork-bot+bluetooth [this message]
2024-02-07 10:19 ` [PATCH net v2 5/9] net: fill in MODULE_DESCRIPTION()s for ipv6 modules Breno Leitao
2024-02-07 11:33 ` Simon Horman
2024-02-07 10:19 ` [PATCH net v2 6/9] net: fill in MODULE_DESCRIPTION()s for ipv4 modules Breno Leitao
2024-02-07 11:42 ` Simon Horman
2024-02-07 10:19 ` [PATCH net v2 7/9] net: fill in MODULE_DESCRIPTION()s for net/sched Breno Leitao
2024-02-07 11:36 ` Simon Horman
2024-02-07 15:37 ` Jakub Kicinski
2024-02-07 21:01 ` Jamal Hadi Salim
2024-02-07 21:27 ` Jamal Hadi Salim
2024-02-07 10:19 ` [PATCH net v2 8/9] net: fill in MODULE_DESCRIPTION()s for ipvtap Breno Leitao
2024-02-07 11:43 ` Simon Horman
2024-02-07 10:19 ` [PATCH net v2 9/9] net: fill in MODULE_DESCRIPTION()s for dsa_loop_bdinfo Breno Leitao
2024-02-07 11:40 ` Simon Horman
2024-02-07 22:21 ` Florian Fainelli
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=170913505272.28471.5112906084108672664.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=alex.aring@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=leitao@debian.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wpan@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 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).