From: Simon Horman <horms@kernel.org>
To: Breno Leitao <leitao@debian.org>
Cc: kuba@kernel.org, davem@davemloft.net, pabeni@redhat.com,
edumazet@google.com,
Steffen Klassert <steffen.klassert@secunet.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
David Ahern <dsahern@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
andrew@lunn.ch
Subject: Re: [PATCH net v2 5/9] net: fill in MODULE_DESCRIPTION()s for ipv6 modules
Date: Wed, 7 Feb 2024 11:33:10 +0000 [thread overview]
Message-ID: <20240207113310.GC1297511@kernel.org> (raw)
In-Reply-To: <20240207101929.484681-6-leitao@debian.org>
On Wed, Feb 07, 2024 at 02:19:24AM -0800, Breno Leitao wrote:
> W=1 builds now warn if module is built without a MODULE_DESCRIPTION().
> Add descriptions to the IPv6 modules.
>
> Signed-off-by: Breno Leitao <leitao@debian.org>
...
> index a7bf0327b380..8820bf5b101a 100644
> --- a/net/ipv6/ip6_udp_tunnel.c
> +++ b/net/ipv6/ip6_udp_tunnel.c
> @@ -182,4 +182,5 @@ struct dst_entry *udp_tunnel6_dst_lookup(struct sk_buff *skb,
> }
> EXPORT_SYMBOL_GPL(udp_tunnel6_dst_lookup);
>
> +MODULE_DESCRIPTION("IPv6 UDP tunnel driver");
> MODULE_LICENSE("GPL");
Hi Breno,
I don't feel strongly about this,
but looking at NET_UDP_TUNNEL and NET_FOU in net/ipv4/Kconfig, maybe:
IPv6 Foo over UDP tunnel driver
Likewise for the change to net/ipv4/udp_tunnel_core.c
in the following patch.
The above not withstanding, this looks good to me.
Reviewed-by: Simon Horman <horms@kernel.org>
...
next prev parent reply other threads:[~2024-02-07 11:33 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
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 [this message]
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=20240207113310.GC1297511@kernel.org \
--to=horms@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=kuba@kernel.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=steffen.klassert@secunet.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.