[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANn89iKzGS39jLrRszBLh6BMyYykX-d_n3egdDU77z_fcXbiXQ@mail.gmail.com>
Date: Mon, 4 Mar 2024 12:49:59 +0100
From: Eric Dumazet <edumazet@...gle.com>
To: Juntong Deng <juntong.deng@...look.com>
Cc: davem@...emloft.net, dsahern@...nel.org, kuba@...nel.org,
pabeni@...hat.com, netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] inet: Add getsockopt support for IP_ROUTER_ALERT and IPV6_ROUTER_ALERT
On Mon, Mar 4, 2024 at 12:33 PM Juntong Deng <juntong.deng@...look.com> wrote:
>
> Currently getsockopt does not support IP_ROUTER_ALERT and
> IPV6_ROUTER_ALERT, and we are unable to get the values of these two
> socket options through getsockopt.
>
> This patch adds getsockopt support for IP_ROUTER_ALERT and
> IPV6_ROUTER_ALERT.
>
> Signed-off-by: Juntong Deng <juntong.deng@...look.com>
>
This looks good to me, thanks, assuming this is net-next material.
Make sure next time to include the target tree (net or net-next)
Reviewed-by: Eric Dumazet <edumazet@...gle.com>
Powered by blists - more mailing lists