From: Jakub Kicinski <kuba@kernel.org>
To: Breno Leitao <leitao@debian.org>
Cc: Jay Vosburgh <jv@jvosburgh.net>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-team@meta.com
Subject: Re: [PATCH net-next] bonding: move utsrelease.h include out of bonding_priv.h
Date: Tue, 17 Mar 2026 18:37:56 -0700 [thread overview]
Message-ID: <20260317183756.33d67d60@kernel.org> (raw)
In-Reply-To: <20260316-bond_uts-v1-1-428696ea79d5@debian.org>
On Mon, 16 Mar 2026 05:17:45 -0700 Breno Leitao wrote:
> +++ b/drivers/net/bonding/bond_procfs.c
> @@ -6,8 +6,11 @@
> #include <net/netns/generic.h>
> #include <net/bonding.h>
>
> +#include <generated/utsrelease.h>
> #include "bonding_priv.h"
Somewhat unfortunate placement, shouldnt it be the first include above
the linux/ ones? If we were going best-effort-alphabetically?
> +#define bond_version DRV_DESCRIPTION ": v" UTS_RELEASE "\n"
> +
> static void *bond_info_seq_start(struct seq_file *seq, loff_t *pos)
> __acquires(RCU)
> {
> diff --git a/drivers/net/bonding/bonding_priv.h b/drivers/net/bonding/bonding_priv.h
> index fef6288c6944f..f9b327b6a494a 100644
> --- a/drivers/net/bonding/bonding_priv.h
> +++ b/drivers/net/bonding/bonding_priv.h
> @@ -12,11 +12,7 @@
>
> #ifndef _BONDING_PRIV_H
> #define _BONDING_PRIV_H
> -#include <generated/utsrelease.h>
> -
> #define DRV_NAME "bonding"
> #define DRV_DESCRIPTION "Ethernet Channel Bonding Driver"
I think this entire header can go, TBH?
DESCRIPTION is used only in main
And DRV_NAME can be replaced by KBUILD_MODNAME where it's used.
> -#define bond_version DRV_DESCRIPTION ": v" UTS_RELEASE "\n"
> -
> #endif
prev parent reply other threads:[~2026-03-18 1:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 12:17 [PATCH net-next] bonding: move utsrelease.h include out of bonding_priv.h Breno Leitao
2026-03-18 1:37 ` Jakub Kicinski [this message]
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=20260317183756.33d67d60@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jv@jvosburgh.net \
--cc=kernel-team@meta.com \
--cc=leitao@debian.org \
--cc=linux-kernel@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.