From: Stephen Hemminger <stephen@networkplumber.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: kys@microsoft.com, haiyangz@microsoft.com,
sthemmin@microsoft.com, devel@linuxdriverproject.org,
netdev@vger.kernel.org
Subject: Re: [PATCH net 2/3] hv_netvsc: fix network namespace issues with VF support
Date: Tue, 12 Jun 2018 08:10:24 -0700 [thread overview]
Message-ID: <20180612081024.140aa5bd@xeon-e3> (raw)
In-Reply-To: <20180612095128.kslkt6ban6otanbs@mwanda>
On Tue, 12 Jun 2018 12:51:28 +0300
Dan Carpenter <dan.carpenter@oracle.com> wrote:
> On Mon, Jun 11, 2018 at 12:44:55PM -0700, Stephen Hemminger wrote:
> > When finding the parent netvsc device, the search needs to be across
> > all netvsc device instances (independent of network namespace).
> >
> > Find parent device of VF using upper_dev_get routine which
> > searches only adjacent list.
> >
> > Fixes: e8ff40d4bff1 ("hv_netvsc: improve VF device matching")
> > Signed-off-by: Stephen Hemminger <sthemmin@microsoft.com>
> >
> > netns aware byref
>
> What? Presumably that wasn't supposed to be part of the commit message.
That was leftover from earlier commit message
next prev parent reply other threads:[~2018-06-12 15:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 19:44 [PATCH net 0/3] hv_netvsc: notification and namespace fixes Stephen Hemminger
2018-06-11 19:44 ` [PATCH net 1/3] hv_netvsc: drop common code until callback model fixed Stephen Hemminger
2018-06-11 19:44 ` [PATCH net 2/3] hv_netvsc: fix network namespace issues with VF support Stephen Hemminger
2018-06-12 9:51 ` Dan Carpenter
2018-06-12 15:10 ` Stephen Hemminger [this message]
2018-06-11 19:44 ` [PATCH net 3/3] hv_netvsc: move VF to same namespace as netvsc device Stephen Hemminger
2018-06-12 22:22 ` [PATCH net 0/3] hv_netvsc: notification and namespace fixes 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=20180612081024.140aa5bd@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dan.carpenter@oracle.com \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=netdev@vger.kernel.org \
--cc=sthemmin@microsoft.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.