From: Hangbin Liu <liuhangbin@gmail.com>
To: Nikolay Aleksandrov <nikolay@nvidia.com>
Cc: netdev@vger.kernel.org, Nikolay Aleksandrov <razor@blackwall.org>,
roopa@nvidia.com, bridge@lists.linux-foundation.org,
davem@davemloft.net, kuba@kernel.org
Subject: Re: [PATCHv2 net] net: bridge: mcast: QRI must be less than QI
Date: Wed, 20 Oct 2021 18:19:25 +0800 [thread overview]
Message-ID: <YW/tLekS17ZF9/w1@Laptop-X1> (raw)
In-Reply-To: <c041a184-92cb-0ebd-25e9-13bfc6413fc9@nvidia.com>
On Wed, Oct 20, 2021 at 12:49:17PM +0300, Nikolay Aleksandrov wrote:
> Nacked-by: Nikolay Aleksandrov <nikolay@nvidia.com>
>
> I think we just discussed this a day ago? It is the same problem -
> while we all agree the values should follow the RFC, users have had
> the option to set any values forever (even non-RFC compliant ones).
> This change risks breaking user-space.
OK, I misunderstood your reply in last mail. I thought you only object to
disabling no meaning values(e.g. set timer to 0, which not is forbid by the
RFC). I don't know you also reject to follow a *MUST* rule defined in the RFC.
>
> Users are free to follow the RFC or not, we can't force them at this
> point. This should've been done when the config option was added long
> time ago.
OK, I will stop working on this path.
Thanks
Hangbin
next prev parent reply other threads:[~2021-10-20 10:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 2:36 [PATCH net] net: bridge: mcast: QRI must be less than QI Hangbin Liu
2021-10-20 2:40 ` [PATCHv2 " Hangbin Liu
2021-10-20 9:49 ` Nikolay Aleksandrov
2021-10-20 10:19 ` Hangbin Liu [this message]
2021-10-20 12:10 ` Hangbin Liu
2021-10-20 12:14 ` Nikolay Aleksandrov
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=YW/tLekS17ZF9/w1@Laptop-X1 \
--to=liuhangbin@gmail.com \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@nvidia.com \
--cc=razor@blackwall.org \
--cc=roopa@nvidia.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