From: David Ahern <dsahern@gmail.com>
To: Rocco Yue <rocco.yue@mediatek.com>
Cc: "David S . Miller" <davem@davemloft.net>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
David Ahern <dsahern@kernel.org>,
Jakub Kicinski <kuba@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, rocco.yue@gmail.com
Subject: Re: [PATCH net-next] net: ipv6: add IFLA_RA_MTU to expose mtu value in the RA message
Date: Thu, 29 Jul 2021 11:28:26 -0600 [thread overview]
Message-ID: <57652c0b-ded8-8386-c9a7-40deb1525db2@gmail.com> (raw)
In-Reply-To: <20210729154251.1380-1-rocco.yue@mediatek.com>
On 7/29/21 9:42 AM, Rocco Yue wrote:
> Because the purpose of this patch is for userspace to correctly read the
> ra_mtu value of different network device, if the DEVCONF is completely dropped,
> does that mean I can add the "ra_mtu" member in the "struct net_device" .
good point. IFLA is the wrong attribute. It should be IFLA_INET6_RA_MTU,
stored in inet6_dev and added to the link message in
inet6_fill_ifla6_attrs.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-07-29 17:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-29 9:02 [PATCH net-next] net: ipv6: add IFLA_RA_MTU to expose mtu value in the RA message Rocco Yue
2021-07-29 14:41 ` David Ahern
2021-07-29 15:42 ` Rocco Yue
2021-07-29 17:28 ` David Ahern [this message]
2021-07-30 17:39 ` Rocco Yue
2021-07-29 14:43 ` David Ahern
2021-07-29 16:45 ` kernel test robot
2021-07-29 18:32 ` kernel test robot
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=57652c0b-ded8-8386-c9a7-40deb1525db2@gmail.com \
--to=dsahern@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=rocco.yue@gmail.com \
--cc=rocco.yue@mediatek.com \
--cc=yoshfuji@linux-ipv6.org \
/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).