From: David Ahern <dsahern@gmail.com>
To: Seth David Schoen <schoen@loyalty.org>,
netdev@vger.kernel.org, John Gilmore <gnu@toad.com>,
Dave Taht <dave.taht@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
David Ahern <dsahern@kernel.org>
Subject: Re: [RESEND PATCH net-next 1/2] ip: Treat IPv4 segment's lowest address as unicast
Date: Thu, 13 May 2021 19:43:04 -0600 [thread overview]
Message-ID: <f59a83c4-838f-ebf8-72d6-e1d66967c596@gmail.com> (raw)
In-Reply-To: <20210513043749.GM1047389@frotz.zork.net>
On 5/12/21 10:37 PM, Seth David Schoen wrote:
> Treat only the highest, not the lowest, IPv4 address within a local
> subnet as a broadcast address.
>
> Signed-off-by: Seth David Schoen <schoen@loyalty.org>
> Suggested-by: John Gilmore <gnu@toad.com>
> Acked-by: Dave Taht <dave.taht@gmail.com>
> ---
> net/ipv4/fib_frontend.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
Reviewed-by: David Ahern <dsahern@kernel.org>
next prev parent reply other threads:[~2021-05-14 1:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-13 4:36 [RESEND PATCH net-next 0/2] Treat IPv4 lowest address as ordinary unicast address Seth David Schoen
2021-05-13 4:37 ` [RESEND PATCH net-next 1/2] ip: Treat IPv4 segment's lowest address as unicast Seth David Schoen
2021-05-14 1:43 ` David Ahern [this message]
2021-05-13 4:38 ` [RESEND PATCH net-next 2/2] selftests: Lowest IPv4 address in a subnet is valid Seth David Schoen
2021-05-14 1:43 ` David Ahern
2021-05-17 21:00 ` [RESEND PATCH net-next 0/2] Treat IPv4 lowest address as ordinary unicast address patchwork-bot+netdevbpf
-- strict thread matches above, loose matches on Subject: below --
2021-05-05 23:25 Seth David Schoen
2021-05-05 23:28 ` [RESEND PATCH net-next 1/2] ip: Treat IPv4 segment's lowest address as unicast Seth David Schoen
2021-05-07 0:36 ` Jakub Kicinski
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=f59a83c4-838f-ebf8-72d6-e1d66967c596@gmail.com \
--to=dsahern@gmail.com \
--cc=dave.taht@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=gnu@toad.com \
--cc=netdev@vger.kernel.org \
--cc=schoen@loyalty.org \
--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 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.