All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Paolo Abeni <pabeni@redhat.com>, netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
	Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
	Edward Cree <ecree@solarflare.com>,
	Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: [PATCH net-next v4 1/5] ipv6: add fib6_has_custom_rules() helper
Date: Thu, 21 Nov 2019 13:07:08 -0700	[thread overview]
Message-ID: <ebf9a1bc-a8f6-a942-a1e9-d247d5b312dd@gmail.com> (raw)
In-Reply-To: <a74feb96efb0d6bec9f1f2598f5773991aa39e26.1574252982.git.pabeni@redhat.com>

On 11/20/19 5:47 AM, Paolo Abeni wrote:
> It wraps the namespace field with the same name, to easily
> access it regardless of build options.
> 
> Suggested-by: David Ahern <dsahern@gmail.com>
> Suggested-by: Eric Dumazet <eric.dumazet@gmail.com>
> Signed-off-by: Paolo Abeni <pabeni@redhat.com>
> ---
>  include/net/ip6_fib.h | 9 +++++++++
>  1 file changed, 9 insertions(+)
> 

Reviewed-by: David Ahern <dsahern@gmail.com>



  reply	other threads:[~2019-11-21 20:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-20 12:47 [PATCH net-next v4 0/5] net: introduce and use route hint Paolo Abeni
2019-11-20 12:47 ` [PATCH net-next v4 1/5] ipv6: add fib6_has_custom_rules() helper Paolo Abeni
2019-11-21 20:07   ` David Ahern [this message]
2019-11-20 12:47 ` [PATCH net-next v4 2/5] ipv6: keep track of routes using src Paolo Abeni
2019-11-21 20:09   ` David Ahern
2019-11-20 12:47 ` [PATCH net-next v4 3/5] ipv6: introduce and uses route look hints for list input Paolo Abeni
2019-11-21 20:11   ` David Ahern
2019-11-20 12:47 ` [PATCH net-next v4 4/5] ipv4: move fib4_has_custom_rules() helper to public header Paolo Abeni
2019-11-21 20:12   ` David Ahern
2019-11-20 12:47 ` [PATCH net-next v4 5/5] ipv4: use dst hint for ipv4 list receive Paolo Abeni
2019-11-21 21:16   ` David Ahern
2019-11-20 16:54 ` [PATCH net-next v4 0/5] net: introduce and use route hint Edward Cree
2019-11-21 22:46 ` David Miller

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=ebf9a1bc-a8f6-a942-a1e9-d247d5b312dd@gmail.com \
    --to=dsahern@gmail.com \
    --cc=davem@davemloft.net \
    --cc=ecree@solarflare.com \
    --cc=eric.dumazet@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=willemdebruijn.kernel@gmail.com \
    /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.