From: Haiyang Zhang <haiyangz@microsoft.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: David Miller <davem@davemloft.net>,
"olaf@aepfle.de" <olaf@aepfle.de>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"driverdev-devel@linuxdriverproject.org"
<driverdev-devel@linuxdriverproject.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH net-next,v4] hyperv: Add support for virtual Receive Side Scaling (vRSS)
Date: Wed, 26 Mar 2014 12:31:24 +0000 [thread overview]
Message-ID: <c7fe8f6655564fcf924521d01d3fa95a@DFM-DB3MBX15-06.exchange.corp.microsoft.com> (raw)
In-Reply-To: <20140326034955.GA10875@kroah.com>
> -----Original Message-----
> From: Greg KH [mailto:gregkh@linuxfoundation.org]
> Sent: Tuesday, March 25, 2014 11:50 PM
> To: Haiyang Zhang
> Cc: David Miller; olaf@aepfle.de; netdev@vger.kernel.org;
> jasowang@redhat.com; driverdev-devel@linuxdriverproject.org; linux-
> kernel@vger.kernel.org
> Subject: Re: [PATCH net-next,v4] hyperv: Add support for virtual Receive
> Side Scaling (vRSS)
>
> On Wed, Mar 26, 2014 at 03:23:47AM +0000, Haiyang Zhang wrote:
> >
> >
> > > -----Original Message-----
> > > From: David Miller [mailto:davem@davemloft.net]
> > > Sent: Tuesday, March 25, 2014 8:47 PM
> > > To: Haiyang Zhang
> > > Cc: netdev@vger.kernel.org; KY Srinivasan; olaf@aepfle.de;
> > > jasowang@redhat.com; linux-kernel@vger.kernel.org; driverdev-
> > > devel@linuxdriverproject.org
> > > Subject: Re: [PATCH net-next,v4] hyperv: Add support for virtual
> Receive
> > > Side Scaling (vRSS)
> > >
> > > From: David Miller <davem@davemloft.net>
> > > Date: Tue, 25 Mar 2014 20:43:43 -0400 (EDT)
> > >
> > > > From: Haiyang Zhang <haiyangz@microsoft.com>
> > > > Date: Tue, 25 Mar 2014 20:37:43 +0000
> > > >
> > > >> Do we know when the dependency (commit: 8a7206a89f) will be
> merged
> > > >> into net-next tree?
> > > >
> > > > You're really not very patient, to say the least.
> > > >
> > > > It's done now and I'm working to integrate your patch.
> > > >
> > > > That patch has been in under review state in patchwork, which
> means
> > > > that I will get to it at some point, so you don't need to worry
> about
> > > > it any more than any other patch you might submit.
> > > >
> > > > The whole reason patchwork exists is so that people don't have to
> > > > ask.
> > >
> > > And actually, this dependency "8a7206a89f" commit doesn't exist
> > > in the 'net' tree at all. I just merged Linus's tree into 'net'
> > > and it doesn't exist there either.
> > >
> > > So this patch still doesn't compile.
> > >
> > > I'm tossing it from patchwork until you sort this out.
> >
> > Dave,
> >
> > Thank you for the efforts.
> > The commit is in the linux-next tree. You can see it from this link:
> > http://git.kernel.org/cgit/linux/kernel/git/next/linux-
> next.git/commit/?id=8a7206a89f85c8439561b0eff85bb9440a2e97a9
> > And, here is the commit log:
> >
> > author
> > K. Y. Srinivasan <kys@microsoft.com> 2014-02-03 20:42:45 (GMT)
> > committer
> > Greg Kroah-Hartman <gregkh@linuxfoundation.org> 2014-02-07 23:22:40
> (GMT)
> > commit
> > 8a7206a89f85c8439561b0eff85bb9440a2e97a9 (patch)
> > tree
> > 61f763919607368481ac128f56416df1f49cd187
> > parent
> > 011a7c3cc3aa60c7ea6bb49d847e80a299ba7b36 (diff)
> >
> > Drivers: hv: vmbus: Support per-channel driver state
> > As we implement Virtual Receive Side Scaling on the networking side
> > (the VRSS patches are currently under review), it will be useful to
> have
> > per-channel state that vmbus drivers can manage. Add support for
> > managing per-channel state.
> >
> > KY:
> > Do you know the original tree this patch was checked into by Greg KH?
> Or,
> > did Greg checked into linux-next tree directly?
>
> No one "checks into the linux-next tree directly".
>
> So your patch relies on a patch in my char-misc tree? Ick, that wasn't
> very wise.
>
> It will just have to wait until the patch goes into 3.15-rc1, as my
> trees are closed, sorry.
Greg,
Thank you for the info. We will wait until KY's earlier patch is merged into
3.15rc1.
In the future, the changes for vmbus or common header used by netvsc driver
should be submitted into net-next tree, correct? So, it can be available quickly
for the subsequent features?
Thanks,
- Haiyang
next prev parent reply other threads:[~2014-03-26 12:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 20:43 Haiyang Zhang
2014-03-25 20:37 ` Haiyang Zhang
2014-03-26 0:43 ` David Miller
2014-03-26 0:47 ` David Miller
2014-03-26 3:23 ` Haiyang Zhang
2014-03-26 3:49 ` Greg KH
2014-03-26 12:31 ` Haiyang Zhang [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-04-21 17:20 Haiyang Zhang
2014-04-21 17:33 ` David Miller
2014-04-07 19:23 Haiyang Zhang
2014-04-07 18:42 ` David Miller
2014-04-07 22:12 ` Sharat Masetty
2014-04-08 15:43 ` Haiyang Zhang
2014-04-17 17:25 ` Haiyang Zhang
2014-04-17 18:17 ` David Miller
2014-04-03 16:05 Haiyang Zhang
2014-04-03 15:15 ` David Miller
2014-04-03 15:17 ` Haiyang Zhang
2014-03-20 22:28 Haiyang Zhang
2014-03-21 18:49 ` David Miller
2014-03-21 18:55 ` David Miller
2014-03-21 19:12 ` Haiyang Zhang
2014-03-21 19:32 ` David Miller
2014-03-21 19:42 ` Haiyang Zhang
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=c7fe8f6655564fcf924521d01d3fa95a@DFM-DB3MBX15-06.exchange.corp.microsoft.com \
--to=haiyangz@microsoft.com \
--cc=davem@davemloft.net \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olaf@aepfle.de \
/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
all inboxes | Powered by JetHome®