[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
<AM6PR03MB5848FE9567FCB44911E8E4D599232@AM6PR03MB5848.eurprd03.prod.outlook.com>
Date: Mon, 4 Mar 2024 20:08:28 +0800
From: Juntong Deng <juntong.deng@...look.com>
To: Eric Dumazet <edumazet@...gle.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 2024/3/4 19:49, Eric Dumazet wrote:
> 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>
Hi Eric Dumazet,
Thanks for the review.
Yes, I made this patch based on net-next.
Sorry for the oversight, I will add the target tree next time.
Powered by blists - more mailing lists