ell.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz at gmail.com>
To: ell at lists.01.org
Subject: Re: [PATCH 04/17] netconfig: Create routes from Router Advertisements
Date: Wed, 18 May 2022 13:42:41 -0500	[thread overview]
Message-ID: <75baec0d-b940-5fd0-2250-99907c641968@gmail.com> (raw)
In-Reply-To: 20220513224713.1447773-4-andrew.zaborowski@intel.com

[-- Attachment #1: Type: text/plain, Size: 1248 bytes --]

Hi Andrew,

On 5/13/22 17:47, Andrew Zaborowski wrote:
> If IPv6 is enabled, create the ICMP6 client and handle Router
> Advertisements received by creating, updating and removing routes per
> the data in the Router Advertisements.  Timeouts aren't handled yet.
> ---
>   ell/netconfig.c | 293 +++++++++++++++++++++++++++++++++++++++++++++---
>   1 file changed, 278 insertions(+), 15 deletions(-)
> 

<snip>

> +static void netconfig_icmp6_event_handler(struct l_icmp6_client *client,
> +						enum l_icmp6_client_event event,
> +						void *event_data,
> +						void *user_data)
> +{
> +	struct l_netconfig *nc = user_data;
> +	const struct l_icmp6_router *r;
> +	struct l_rtnl_route *default_route;
> +	unsigned int i;
> +
> +	if (event != L_ICMP6_CLIENT_EVENT_ROUTER_FOUND)
> +		return;
> +
> +	r = event_data;
> +
> +	/*
> +	 * Note: If this is the first RA received, the l_dhcp6_client
> +	 * will have received the event before us and will be acting
> +	 * on it by now.
> +	 */
> +
> +	if (nc->v4_gateway_override)
> +		return;
> +

So I think you meant v6_gateway_override here and I fixed this up accordingly. 
Send a fix if this wasn't correct.

Patches 1-4 applied, thanks.

Regards,
-Denis

             reply	other threads:[~2022-05-18 18:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-18 18:42 Denis Kenzior [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-05-13 22:47 [PATCH 04/17] netconfig: Create routes from Router Advertisements Andrew Zaborowski
2022-05-13 14:54 Andrew Zaborowski

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=75baec0d-b940-5fd0-2250-99907c641968@gmail.com \
    --to=ell@lists.linux.dev \
    /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;
as well as URLs for NNTP newsgroup(s).