netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: dsahern@kernel.org
Cc: netdev@vger.kernel.org, dsahern@gmail.com
Subject: Re: [PATCH v2 net-next 0/3] net: Update fib_table_lookup tracepoints
Date: Thu, 24 May 2018 23:01:37 -0400 (EDT)	[thread overview]
Message-ID: <20180524.230137.1807669884179615246.davem@davemloft.net> (raw)
In-Reply-To: <20180524000849.6553-1-dsahern@kernel.org>

From: dsahern@kernel.org
Date: Wed, 23 May 2018 17:08:46 -0700

> From: David Ahern <dsahern@gmail.com>
> 
> Update the FIB lookup tracepoints to include ip proto and port fields
> from the flow struct. In the process make the IPv4 tracepoint inline
> with IPv6 which is much easier to use and follow the lookup and result.
> 
> Remove the tracepoint in fib_validate_source which does not provide
> value above the fib_table_lookup which immediately follows it.
> 
> v2
> - move CREATE_TRACE_POINTS for the v6 tracepoint to route.c to handle
>   its need for an internal function to convert route type to error and
>   handle IPv6 as a module or builtin. Reported by kbuild robot.

Series applied.

      parent reply	other threads:[~2018-05-25  3:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-24  0:08 [PATCH v2 net-next 0/3] net: Update fib_table_lookup tracepoints dsahern
2018-05-24  0:08 ` [PATCH v2 net-next 1/3] net/ipv4: Udate fib_table_lookup tracepoint dsahern
2018-05-24  0:08 ` [PATCH v2 net-next 2/3] net/ipv6: Udate fib6_table_lookup tracepoint dsahern
2018-05-24  0:08 ` [PATCH v2 net-next 3/3] net/ipv4: Remove tracepoint in fib_validate_source dsahern
2018-05-25  3:01 ` David Miller [this message]

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=20180524.230137.1807669884179615246.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=dsahern@gmail.com \
    --cc=dsahern@kernel.org \
    --cc=netdev@vger.kernel.org \
    /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).