On Mon, Mar 4, 2024 at 12:33 PM Juntong Deng <[email protected]> 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 <[email protected]>
>
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 <[email protected]>
On 2024/3/4 19:49, Eric Dumazet wrote:
> On Mon, Mar 4, 2024 at 12:33 PM Juntong Deng <[email protected]> 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 <[email protected]>
>>
>
> 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 <[email protected]>
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.