All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roopa Prabhu <roopa@cumulusnetworks.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, dsa@cumulusnetworks.com, idosch@idosch.org
Subject: [PATCH net-next v2 0/2] fib rules extack support
Date: Sat, 21 Apr 2018 09:41:29 -0700	[thread overview]
Message-ID: <1524328891-3647-1-git-send-email-roopa@cumulusnetworks.com> (raw)

From: Roopa Prabhu <roopa@cumulusnetworks.com>

First patch refactors code to move fib rule netlink handling
into a common function. This became obvious when adding
duplicate extack msgs in add and del paths. Second patch
adds extack msgs.

v2 - Dropped the ip route get support and selftests from
     the series to look at the input path some more (as pointed
     out by ido). Will come back to that next week when i have
     some time. resending just the extack part for now.

Roopa Prabhu (2):
  fib_rules: move common handling of newrule delrule msgs into
    fib_nl2rule
  net: fib_rules: add extack support

 include/net/fib_rules.h |   3 +-
 net/core/fib_rules.c    | 471 +++++++++++++++++++++++-------------------------
 net/decnet/dn_rules.c   |   7 +-
 net/ipv4/fib_rules.c    |   7 +-
 net/ipv4/ipmr.c         |   3 +-
 net/ipv6/fib6_rules.c   |   7 +-
 net/ipv6/ip6mr.c        |   3 +-
 7 files changed, 245 insertions(+), 256 deletions(-)

-- 
2.1.4

             reply	other threads:[~2018-04-21 16:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-21 16:41 Roopa Prabhu [this message]
2018-04-21 16:41 ` [PATCH net-next v2 1/2] fib_rules: move common handling of newrule delrule msgs into fib_nl2rule Roopa Prabhu
2018-04-21 16:41 ` [PATCH net-next v2 2/2] net: fib_rules: add extack support Roopa Prabhu
2018-05-08  5:29   ` [lkp-robot] [net] 69d73ea95c: kernel_selftests.net.fib-onlink-tests.sh.fail kernel test robot
2018-05-09 17:46     ` Roopa Prabhu
2018-04-23 14:21 ` [PATCH net-next v2 0/2] fib rules extack support David Miller
2018-04-24  3:19   ` Roopa Prabhu

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=1524328891-3647-1-git-send-email-roopa@cumulusnetworks.com \
    --to=roopa@cumulusnetworks.com \
    --cc=davem@davemloft.net \
    --cc=dsa@cumulusnetworks.com \
    --cc=idosch@idosch.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 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.