From: David Miller <davem@davemloft.net>
To: dsahern@gmail.com
Cc: netdev@vger.kernel.org, j.vosburgh@gmail.com, vfalico@gmail.com,
andy@greyhouse.net, jiri@mellanox.com, idosch@mellanox.com,
bridge@lists.linux-foundation.org
Subject: Re: [PATCH v2 net-next 0/7] net: Plumb extack error reporting to enslavements
Date: Wed, 04 Oct 2017 21:42:17 -0700 (PDT) [thread overview]
Message-ID: <20171004.214217.633098016702209791.davem@davemloft.net> (raw)
In-Reply-To: <1507164531-17732-1-git-send-email-dsahern@gmail.com>
From: David Ahern <dsahern@gmail.com>
Date: Wed, 4 Oct 2017 17:48:44 -0700
> Another round of extending extack error reporting, this time for
> enslavements through ndo_add_slave and notifiers.
>
> v2
> - changed how the messages are added to bonding driver per Jiri's request
> - fixed spectrum message for LAG overflow per Ido's comment
Series applied, thanks David.
prev parent reply other threads:[~2017-10-05 4:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 0:48 [PATCH v2 net-next 0/7] net: Plumb extack error reporting to enslavements David Ahern
2017-10-05 0:48 ` [PATCH v2 net-next 1/7] net: Add extack to netdev_notifier_info David Ahern
2017-10-05 0:48 ` [PATCH v2 net-next 2/7] net: Add extack to ndo_add_slave David Ahern
2017-10-05 0:48 ` [PATCH v2 net-next 3/7] net: Add extack to upper device linking David Ahern
2017-10-05 0:48 ` [PATCH v2 net-next 4/7] net: vrf: Add extack messages for enslave errors David Ahern
2017-10-05 0:48 ` [PATCH v2 net-next 5/7] net: bonding: Add extack messages for some enslave failures David Ahern
2017-10-05 0:48 ` [PATCH v2 net-next 6/7] net: bridge: Pass extack to down to netdev_master_upper_dev_link David Ahern
2017-10-05 0:48 ` [PATCH v2 net-next 7/7] mlxsw: spectrum: Add extack messages for enslave failures David Ahern
2017-10-05 4:42 ` 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=20171004.214217.633098016702209791.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andy@greyhouse.net \
--cc=bridge@lists.linux-foundation.org \
--cc=dsahern@gmail.com \
--cc=idosch@mellanox.com \
--cc=j.vosburgh@gmail.com \
--cc=jiri@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=vfalico@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox