From: Bhavesh Davda <bhavesh@vmware•com>
To: Randy Dunlap <randy.dunlap@oracle•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
netdev <netdev@vger•kernel.org>,
Shreyas Bhatewara <sbhatewara@vmware•com>,
"pv-drivers@vmware•com" <pv-drivers@vmware•com>,
"linux-next@vger•kernel.org" <linux-next@vger•kernel.org>,
LKML <linux-kernel@vger•kernel.org>,
"davem@davemloft•net" <davem@davemloft•net>
Subject: Re: [Pv-drivers] [PATCH -next] vmxnet: fix 2 build problems
Date: Wed, 14 Oct 2009 19:00:45 -0700 [thread overview]
Message-ID: <06257446-AA46-489A-80D7-D7C70096A744@vmware.com> (raw)
In-Reply-To: <20091014181715.09a82630.randy.dunlap@oracle.com>
Looks great! Thanks for making this change!
Signed-off-by: Bhavesh davda <bhavesh@vmware.com<mailto:bhavesh@vmware•com>>
- Bhavesh
I'm usually not as bad with my spelling as my iPhone makes it appear.
On Oct 14, 2009, at 6:18 PM, "Randy Dunlap" <randy.dunlap@oracle.com<mailto:randy.dunlap@oracle•com>> wrote:
Signed-off-by: Randy Dunlap <<mailto:randy.dunlap@oracle.com>randy.dunlap@oracle.com<mailto:randy.dunlap@oracle•com>>
next prev parent reply other threads:[~2009-10-15 2:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-14 5:34 linux-next: Tree for October 14 Stephen Rothwell
2009-10-14 15:55 ` Randy Dunlap
2009-10-14 21:12 ` Stephen Rothwell
2009-10-14 22:10 ` [PATCH -next] ia64/sn: fix percpu warnings Randy Dunlap
2009-10-15 1:33 ` Tejun Heo
2009-10-26 18:24 ` Tony Luck
2009-10-26 23:35 ` Luck, Tony
2009-10-28 15:03 ` Tejun Heo
2009-10-28 16:24 ` Luck, Tony
2009-10-28 16:37 ` Tejun Heo
2009-10-28 16:58 ` Luck, Tony
2009-10-28 22:23 ` Luck, Tony
2009-10-29 14:43 ` Tejun Heo
2009-10-29 15:43 ` Tejun Heo
2009-10-30 16:05 ` Jan Beulich
2009-10-14 22:10 ` [PATCH -next] kvm: fix ia64 printk formats Randy Dunlap
2009-10-15 2:32 ` Zhang, Xiantao
2009-10-15 1:17 ` [PATCH -next] vmxnet: fix 2 build problems Randy Dunlap
2009-10-15 2:00 ` Bhavesh Davda [this message]
2009-10-15 3:39 ` [Pv-drivers] " 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=06257446-AA46-489A-80D7-D7C70096A744@vmware.com \
--to=bhavesh@vmware$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pv-drivers@vmware$(echo .)com \
--cc=randy.dunlap@oracle$(echo .)com \
--cc=sbhatewara@vmware$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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