All of lore.kernel.org
 help / color / mirror / Atom feed
From: Breno Leitao <leitao@debian.org>
To: kuba@kernel.org, davem@davemloft.net, pabeni@redhat.com,
	edumazet@google.com, Alexander Aring <alex.aring@gmail.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	horms@kernel.org, andrew@lunn.ch, f.fainelli@gmail.com,
	jhs@mojatatu.com, Alexander Aring <aahringo@redhat.com>,
	linux-bluetooth@vger.kernel.org (open list:6LOWPAN GENERIC
	(BTLE/IEEE 802.15.4)),
	linux-wpan@vger.kernel.org (open list:6LOWPAN GENERIC (BTLE/IEEE
	802.15.4))
Subject: [PATCH net v3 4/9] net: fill in MODULE_DESCRIPTION()s for 6LoWPAN
Date: Thu,  8 Feb 2024 08:42:39 -0800	[thread overview]
Message-ID: <20240208164244.3818498-5-leitao@debian.org> (raw)
In-Reply-To: <20240208164244.3818498-1-leitao@debian.org>

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>
Acked-by: Alexander Aring <aahringo@redhat.com>
Reviewed-by: Simon Horman <horms@kernel.org>
---
 net/6lowpan/core.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/net/6lowpan/core.c b/net/6lowpan/core.c
index 7b3341cef926..850d4a185f55 100644
--- a/net/6lowpan/core.c
+++ b/net/6lowpan/core.c
@@ -179,4 +179,5 @@ static void __exit lowpan_module_exit(void)
 module_init(lowpan_module_init);
 module_exit(lowpan_module_exit);
 
+MODULE_DESCRIPTION("IPv6 over Low-Power Wireless Personal Area Network core module");
 MODULE_LICENSE("GPL");
-- 
2.39.3


  parent reply	other threads:[~2024-02-08 16:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-08 16:42 [PATCH net v3 0/9] net: Fix MODULE_DESCRIPTION() for net (p5) Breno Leitao
2024-02-08 16:42 ` [PATCH net v3 1/9] net: fill in MODULE_DESCRIPTION()s for xfrm Breno Leitao
2024-02-08 16:42 ` [PATCH net v3 2/9] net: fill in MODULE_DESCRIPTION()s for mpoa Breno Leitao
2024-02-08 16:42 ` [PATCH net v3 3/9] net: fill in MODULE_DESCRIPTION()s for af_key Breno Leitao
2024-02-08 16:42 ` Breno Leitao [this message]
2024-02-28 15:44   ` [PATCH net v3 4/9] net: fill in MODULE_DESCRIPTION()s for 6LoWPAN patchwork-bot+bluetooth
2024-02-08 16:42 ` [PATCH net v3 5/9] net: fill in MODULE_DESCRIPTION()s for ipv6 modules Breno Leitao
2024-02-08 16:42 ` [PATCH net v3 6/9] net: fill in MODULE_DESCRIPTION()s for ipv4 modules Breno Leitao
2024-02-08 16:42 ` [PATCH net v3 7/9] net: fill in MODULE_DESCRIPTION()s for net/sched Breno Leitao
2024-02-08 22:11   ` Jamal Hadi Salim
2024-02-08 16:42 ` [PATCH net v3 8/9] net: fill in MODULE_DESCRIPTION()s for ipvtap Breno Leitao
2024-02-08 16:42 ` [PATCH net v3 9/9] net: fill in MODULE_DESCRIPTION()s for dsa_loop_bdinfo Breno Leitao
2024-02-08 23:37   ` Florian Fainelli
2024-02-09 22:20 ` [PATCH net v3 0/9] net: Fix MODULE_DESCRIPTION() for net (p5) 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=20240208164244.3818498-5-leitao@debian.org \
    --to=leitao@debian.org \
    --cc=aahringo@redhat.com \
    --cc=alex.aring@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=horms@kernel.org \
    --cc=jhs@mojatatu.com \
    --cc=kuba@kernel.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 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.