netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: sbhatewara@vmware.com
Cc: netdev@vger.kernel.org, weiyi.huang@gmail.com, pv-drivers@vmware.com
Subject: Re: [PATCH] vmxnet3: remove duplicate #include
Date: Wed, 28 Oct 2009 22:52:17 -0700 (PDT)	[thread overview]
Message-ID: <20091028.225217.78322944.davem@davemloft.net> (raw)
In-Reply-To: <20091028.222901.187567993.davem@davemloft.net>

From: David Miller <davem@davemloft.net>
Date: Wed, 28 Oct 2009 22:29:01 -0700 (PDT)

> From: Shreyas Bhatewara <sbhatewara@vmware.com>
> Date: Wed, 28 Oct 2009 09:30:40 -0700 (PDT)
> 
>> 
>> Remove duplicate headerfile includes from vmxnet3_int.h
>> 
>> Signed-off-by: Shreyas Bhatewara <sbhatewara@vmware.com>
>> Signed-off-by: Huang Weiyi <weiyi.huang@gmail.com>
>> Signed-off-by: Bhavesh Davda <davda@vmware.com>
> 
> Applied.

Guys, I'd like to remove the X86 Kconfig requirement for this
driver.  There really isn't any x86 specific code in the
driver, it uses only standard PCI and networking APIs to function.

I know the virtual hardware won't be seen on other platforms,
but allowing the driver to get build tested on non-x86 platforms
helps me a lot.  I do all of my build verifications on sparc64
for example.

  reply	other threads:[~2009-10-29  5:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-28 16:30 [PATCH] vmxnet3: remove duplicate #include Shreyas Bhatewara
2009-10-28 16:32 ` [Pv-drivers] " Bhavesh Davda
2009-10-29  5:29 ` David Miller
2009-10-29  5:52   ` David Miller [this message]
2009-10-29 13:35     ` [Pv-drivers] " Bhavesh Davda
2009-10-29 13:50       ` David Miller
2009-10-29 17:06         ` Shreyas Bhatewara
2009-11-16 23:41 ` [PATCH 2.6.32-rc3] net: Getting rid of the x86 dependency to built vmxnet3 Shreyas Bhatewara
2009-11-17 12:09   ` 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=20091028.225217.78322944.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=pv-drivers@vmware.com \
    --cc=sbhatewara@vmware.com \
    --cc=weiyi.huang@gmail.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 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).