From: Stephen Hemminger <stephen@networkplumber.org>
To: Mrinmoy Ghosh <mrghosh@cisco.com>
Cc: netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
mrinmoy_g@hotmail.com, Mike Mallin <mmallin@cisco.com>,
Patrice Brissette <pbrisset@cisco.com>
Subject: Re: [PATCH iproute2] bridge:fdb: Protocol field in bridge fdb
Date: Sat, 16 Aug 2025 09:20:51 -0700 [thread overview]
Message-ID: <20250816092051.1a8e4ed3@hermes.local> (raw)
In-Reply-To: <20250816031145.1153429-1-mrghosh@cisco.com>
On Sat, 16 Aug 2025 03:11:45 +0000
Mrinmoy Ghosh <mrghosh@cisco.com> wrote:
> diff --git a/include/uapi/linux/rtnetlink.h b/include/uapi/linux/rtnetlink.h
> index 085bb139..1ff9dbee 100644
> --- a/include/uapi/linux/rtnetlink.h
> +++ b/include/uapi/linux/rtnetlink.h
> @@ -314,6 +314,7 @@ enum {
> #define RTPROT_OSPF 188 /* OSPF Routes */
> #define RTPROT_RIP 189 /* RIP Routes */
> #define RTPROT_EIGRP 192 /* EIGRP Routes */
> +#define RTPROT_HW 193 /* HW Generated Routes */
>
> /* rtm_scope
>
> diff --git a/lib/rt_names.c b/lib/rt_names.c
> index 7dc194b1..b9bc1b50 100644
> --- a/lib/rt_names.c
> +++ b/lib/rt_names.c
> @@ -148,6 +148,7 @@ static char *rtnl_rtprot_tab[256] = {
> [RTPROT_OSPF] = "ospf",
> [RTPROT_RIP] = "rip",
> [RTPROT_EIGRP] = "eigrp",
> + [RTPROT_HW] = "hw",
> };
>
> struct tabhash {
This is iproute2-next material.
Where is the kernel patch for this?
Iproute headers are synced from kernel headers.
If you add new RTPROT entry also need new line into etc/iproute2/rt_protos
next prev parent reply other threads:[~2025-08-16 16:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-16 3:11 [PATCH iproute2] bridge:fdb: Protocol field in bridge fdb Mrinmoy Ghosh
2025-08-16 16:20 ` Stephen Hemminger [this message]
2025-08-18 19:47 ` Mrinmoy Ghosh (mrghosh)
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=20250816092051.1a8e4ed3@hermes.local \
--to=stephen@networkplumber.org \
--cc=bridge@lists.linux-foundation.org \
--cc=mmallin@cisco.com \
--cc=mrghosh@cisco.com \
--cc=mrinmoy_g@hotmail.com \
--cc=netdev@vger.kernel.org \
--cc=pbrisset@cisco.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