From: David Miller <davem@davemloft.net>
To: jiri@resnulli.us
Cc: jakub.kicinski@netronome.com, netdev@vger.kernel.org,
oss-drivers@netronome.com
Subject: Re: [PATCH net-next v2 0/6] nfp: devlink port implementation
Date: Fri, 26 May 2017 11:02:04 -0400 (EDT) [thread overview]
Message-ID: <20170526.110204.1579570229962355609.davem@davemloft.net> (raw)
In-Reply-To: <20170526082532.GC1898@nanopsycho>
From: Jiri Pirko <jiri@resnulli.us>
Date: Fri, 26 May 2017 10:25:32 +0200
> Fri, May 26, 2017 at 10:03:30AM CEST, jakub.kicinski@netronome.com wrote:
>>Hi!
>>
>>This series adds basic devlink support. The operations we can perform
>>are port show and port split/unsplit.
>>
>>v2:
>>Register devlink first, and then register all the ports. Port {,un}split
>>searches the port list, which is protected by a mutex. If port split
>>is requested before ports are registered we will simply not find the port
>>and return -EINVAL.
>
> Looks fine to me now. Thanks!
Wow, you review stuff fast :-)
Series applied, thanks.
next prev parent reply other threads:[~2017-05-26 15:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 8:03 [PATCH net-next v2 0/6] nfp: devlink port implementation Jakub Kicinski
2017-05-26 8:03 ` [PATCH net-next v2 1/6] nfp: move mutex init out of net code Jakub Kicinski
2017-05-26 8:03 ` [PATCH net-next v2 2/6] nfp: add devlink support Jakub Kicinski
2017-05-26 8:03 ` [PATCH net-next v2 3/6] nfp: add helper for cleaning up vNICs Jakub Kicinski
2017-05-26 8:03 ` [PATCH net-next v2 4/6] nfp: register ports as devlink ports Jakub Kicinski
2017-05-26 8:03 ` [PATCH net-next v2 5/6] nfp: calculate total port lanes for split Jakub Kicinski
2017-05-26 8:03 ` [PATCH net-next v2 6/6] nfp: support port splitting via devlink Jakub Kicinski
2017-05-26 8:25 ` [PATCH net-next v2 0/6] nfp: devlink port implementation Jiri Pirko
2017-05-26 15:02 ` David Miller [this message]
2017-05-26 15:00 ` 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=20170526.110204.1579570229962355609.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jakub.kicinski@netronome.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.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