linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Matthias Schiffer <mschiffer@universe-factory.net>,
	dledford@redhat.com, sean.hefty@intel.com,
	hal.rosenstock@gmail.com, j.vosburgh@gmail.com,
	vfalico@gmail.com, andy@greyhouse.net,
	dmitry.tarnyagin@lockless.no, wg@grandegger.com,
	mkl@pengutronix.de, pablo@netfilter.org, laforge@gnumonks.org,
	paulus@samba.org, jiri@resnulli.us, dsa@cumulusnetworks.com,
	shm@cumulusnetworks.com, davem@davemloft.net,
	stephen@networkplumber.org, arvid.brodin@alten.se,
	alex.aring@gmail.com, stefan@osg.samsung.com,
	kuznet@ms2.inr.ac.ru, jmorris@namei.org, yoshfuji@linux-ipv6.org,
	kaber@trash.net, steffen.klassert@secunet.com,
	herbert@gondor.apana.org.au, johannes@sipsolutions.net
Cc: linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, linux-can@vger.kernel.org,
	osmocom-net-gprs@lists.osmocom.org, linux-ppp@vger.kernel.org,
	linux-wpan@vger.kernel.org
Subject: Re: [PATCH net-next] net: add netlink_ext_ack support to rtnl_link_ops
Date: Sat, 24 Jun 2017 20:50:24 -0600	[thread overview]
Message-ID: <1bfb7a80-a440-f960-1f35-a70542106cfb@gmail.com> (raw)
In-Reply-To: <01256ebba091f2108ebeff43e61305bb533067d4.1498303258.git.mschiffer@universe-factory.net>

On 6/24/17 5:35 AM, Matthias Schiffer wrote:
> The following functions are extended with a netlink_ext_ack argument to
> allow extended error reporting:
> 
> * validate
> * newlink
> * changelink
> * slave_validate
> * slave_changelink

I would prefer separate patches for validate, slave_validate, newlink,
changelink, and slave_changelink. I do not believe there is a reason to
lump them into 1 giant patch.

  reply	other threads:[~2017-06-25  2:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-24 11:35 [PATCH net-next] net: add netlink_ext_ack support to rtnl_link_ops Matthias Schiffer
2017-06-25  2:50 ` David Ahern [this message]
2017-06-25 15:50 ` 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=1bfb7a80-a440-f960-1f35-a70542106cfb@gmail.com \
    --to=dsahern@gmail.com \
    --cc=alex.aring@gmail.com \
    --cc=andy@greyhouse.net \
    --cc=arvid.brodin@alten.se \
    --cc=davem@davemloft.net \
    --cc=dledford@redhat.com \
    --cc=dmitry.tarnyagin@lockless.no \
    --cc=dsa@cumulusnetworks.com \
    --cc=hal.rosenstock@gmail.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=j.vosburgh@gmail.com \
    --cc=jiri@resnulli.us \
    --cc=jmorris@namei.org \
    --cc=johannes@sipsolutions.net \
    --cc=kaber@trash.net \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=laforge@gnumonks.org \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-ppp@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=linux-wpan@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=mschiffer@universe-factory.net \
    --cc=netdev@vger.kernel.org \
    --cc=osmocom-net-gprs@lists.osmocom.org \
    --cc=pablo@netfilter.org \
    --cc=paulus@samba.org \
    --cc=sean.hefty@intel.com \
    --cc=shm@cumulusnetworks.com \
    --cc=stefan@osg.samsung.com \
    --cc=steffen.klassert@secunet.com \
    --cc=stephen@networkplumber.org \
    --cc=vfalico@gmail.com \
    --cc=wg@grandegger.com \
    --cc=yoshfuji@linux-ipv6.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).