From: David Miller <davem@davemloft.net>
To: petrm@mellanox.com
Cc: netdev@vger.kernel.org, jiri@mellanox.com, idosch@mellanox.com,
dsa@cumulusnetworks.com
Subject: Re: [PATCH net-next v2 0/8] Pass extack to NETDEV_PRE_UP
Date: Thu, 06 Dec 2018 13:31:59 -0800 (PST) [thread overview]
Message-ID: <20181206.133159.931519302250382081.davem@davemloft.net> (raw)
In-Reply-To: <cover.1544115501.git.petrm@mellanox.com>
From: Petr Machata <petrm@mellanox.com>
Date: Thu, 6 Dec 2018 17:05:35 +0000
> Drivers may need to validate configuration of a device that's about to
> be upped. An example is mlxsw, which needs to check the configuration of
> a VXLAN device attached to an offloaded bridge. Should the validation
> fail, there's currently no way to communicate details of the failure to
> the user, beyond an error number.
>
> Therefore this patch set extends the NETDEV_PRE_UP event to include
> extack, if available.
...
Series applied, thank you.
prev parent reply other threads:[~2018-12-06 21:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 17:05 [PATCH net-next v2 0/8] Pass extack to NETDEV_PRE_UP Petr Machata
2018-12-06 17:05 ` [PATCH net-next v2 1/8] net: core: dev: Add extack argument to dev_open() Petr Machata
2018-12-06 17:05 ` [PATCH net-next v2 2/8] net: vrf: cycle_netdev(): Add an extack argument Petr Machata
2018-12-06 17:05 ` [PATCH net-next v2 3/8] net: ipvlan: ipvlan_set_port_mode(): " Petr Machata
2018-12-06 17:05 ` [PATCH net-next v2 4/8] net: core: dev: Add extack argument to dev_change_flags() Petr Machata
2018-12-06 17:05 ` [PATCH net-next v2 5/8] net: core: dev: Add extack argument to __dev_change_flags() Petr Machata
2018-12-06 17:05 ` [PATCH net-next v2 6/8] net: core: dev: Add call_netdevice_notifiers_extack() Petr Machata
2018-12-06 17:05 ` [PATCH net-next v2 7/8] net: core: dev: Attach extack to NETDEV_PRE_UP Petr Machata
2018-12-06 17:05 ` [PATCH net-next v2 8/8] selftests: mlxsw: Add a new test extack.sh Petr Machata
2018-12-06 21:31 ` 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=20181206.133159.931519302250382081.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dsa@cumulusnetworks.com \
--cc=idosch@mellanox.com \
--cc=jiri@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=petrm@mellanox.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.