From: David Miller <davem@davemloft.net>
To: akataria@vmware.com
Cc: greg@kroah.com, sbhatewara@vmware.com, pv-drivers@vmware.com,
netdev@vger.kernel.org, shemminger@linux-foundation.org,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org, chrisw@sous-sol.org,
anthony@codemonkey.ws, akpm@linux-foundation.org,
jgarzik@pobox.com
Subject: Re: [Pv-drivers] [PATCH 2.6.31-rc9] net: VMware virtual Ethernet NIC driver: vmxnet3
Date: Mon, 28 Sep 2009 18:17:02 -0700 (PDT) [thread overview]
Message-ID: <20090928.181702.41922043.davem@davemloft.net> (raw)
In-Reply-To: <1254185499.13456.40.camel@ank32.eng.vmware.com>
From: Alok Kataria <akataria@vmware.com>
Date: Mon, 28 Sep 2009 17:51:39 -0700
> As a side note, were there any changes in the networking API's, that we
> should look out for in the merge cycle ?
> If not I think the rebase should be pretty trivial.
Just off the top of my head, the return type of the driver transmit
function was changed to netdev_tx_t, for one thing.
But there were likely numerous others. You'll have to check.
next prev parent reply other threads:[~2009-09-29 1:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-28 23:56 [PATCH 2.6.31-rc9] net: VMware virtual Ethernet NIC driver: vmxnet3 Shreyas Bhatewara
2009-09-29 0:08 ` David Miller
2009-09-29 16:37 ` Shreyas Bhatewara
2009-09-29 0:20 ` Greg KH
2009-09-29 0:47 ` [Pv-drivers] " Alok Kataria
2009-09-29 0:22 ` Greg KH
2009-09-29 0:51 ` [Pv-drivers] " Alok Kataria
2009-09-29 1:17 ` David Miller [this message]
2009-09-29 8:53 ` Chris Wright
2009-09-29 13:05 ` Arnd Bergmann
2009-09-29 19:52 ` [Pv-drivers] " Bhavesh Davda
2009-09-29 19:55 ` David Miller
2009-09-29 21:23 ` Arnd Bergmann
2009-09-29 19:45 ` Bhavesh Davda
2009-09-29 20:30 ` Chris Wright
2009-09-29 21:00 ` Bhavesh Davda
2009-09-29 21:54 ` Chris Wright
2009-09-29 20:56 ` Shreyas Bhatewara
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=20090928.181702.41922043.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akataria@vmware.com \
--cc=akpm@linux-foundation.org \
--cc=anthony@codemonkey.ws \
--cc=chrisw@sous-sol.org \
--cc=greg@kroah.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pv-drivers@vmware.com \
--cc=sbhatewara@vmware.com \
--cc=shemminger@linux-foundation.org \
--cc=virtualization@lists.linux-foundation.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).