From: Or Gerlitz <or.gerlitz@gmail.com>
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
stephen@networkplumber.org, Narendra_K@dell.com,
bhutchings@solarflare.com, john.r.fastabend@intel.com
Subject: Re: [patch net-next v3 1/3] net: add ndo to get id of physical port of the device
Date: Mon, 22 Jul 2013 21:37:25 +0300 [thread overview]
Message-ID: <CAJZOPZLHvgBzu2EuLw5ZWvrSFBsmESOVZQEgX91YH1PdfpsJbA@mail.gmail.com> (raw)
In-Reply-To: <20130722180141.GA1498@minipsycho.orion>
On Mon, Jul 22, 2013 at 9:01 PM, Jiri Pirko <jiri@resnulli.us> wrote:
> I have almost done implementation for igb/igbvf (consulting with Intel
> guys) and I'm working on bnx2x NPAR as well (consulting with Broadcom). I
> will post these patches soon.
good, I would prefer to have at least one driver patch as part of the
initial series, as typically done when adding e.g new ndo entry, makes
sense?
Or.
next prev parent reply other threads:[~2013-07-22 18:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 13:05 [patch net-next v3 0/3] export device physical port id to userspace Jiri Pirko
2013-07-22 13:05 ` [patch net-next v3 1/3] net: add ndo to get id of physical port of the device Jiri Pirko
2013-07-22 13:44 ` Narendra_K
2013-07-22 15:59 ` Or Gerlitz
2013-07-22 18:01 ` Jiri Pirko
2013-07-22 18:37 ` Or Gerlitz [this message]
2013-07-22 13:05 ` [patch net-next v3 2/3] rtnl: export physical port id via RT netlink Jiri Pirko
2013-07-22 13:05 ` [patch net-next v3 3/3] net: export physical port id via sysfs Jiri Pirko
2013-07-24 23:01 ` David Miller
2013-07-24 23:00 ` [patch net-next v3 0/3] export device physical port id to userspace David Miller
2013-07-25 7:41 ` Jiri Pirko
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=CAJZOPZLHvgBzu2EuLw5ZWvrSFBsmESOVZQEgX91YH1PdfpsJbA@mail.gmail.com \
--to=or.gerlitz@gmail.com \
--cc=Narendra_K@dell.com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=jiri@resnulli.us \
--cc=john.r.fastabend@intel.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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).