From: "Rose, Gregory V" <gregory.v.rose@intel.com>
To: Alexander Kolesen <kolesen.a@gmail.com>,
Or Gerlitz <or.gerlitz@gmail.com>
Cc: "Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Li, Sibai" <sibai.li@intel.com>
Subject: RE: ixgbe: compilation failed if CONFIG_PCI_IOV isn't set
Date: Mon, 7 Nov 2011 08:47:09 -0800 [thread overview]
Message-ID: <43F901BD926A4E43B106BF17856F075501A1CCA39D@orsmsx508.amr.corp.intel.com> (raw)
In-Reply-To: <20111107124641.GB28044@vaio>
> -----Original Message-----
> From: Alexander Kolesen [mailto:kolesen.a@gmail.com]
> Sent: Monday, November 07, 2011 4:47 AM
> To: Or Gerlitz
> Cc: Kirsher, Jeffrey T; netdev@vger.kernel.org; Rose, Gregory V; Li, Sibai
> Subject: Re: ixgbe: compilation failed if CONFIG_PCI_IOV isn't set
>
> > On Sun, Nov 6, 2011 at 5:18 AM, Jeff Kirsher
> > <jeffrey.t.kirsher@intel.com> wrote:
> > > Was with the latest kernel from David Miller's net.gt tree? I just
> ask
> > > because I just pushed a patch (a couple of days ago) to resolve
> > > compilation errors when CONFIG_PCI_IOV is not enabled by Greg Rose.
> >
> > In my case it was with Linus tree from github
> >
> > Or.
> It was with Linus tree, but David Miller's net.gt alsa has this issue.
Yeah, I'll have it fixed soon. My apologies.
- Greg
prev parent reply other threads:[~2011-11-07 16:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-06 0:08 ixgbe: compilation failed if CONFIG_PCI_IOV isn't set Alexander Kolesen
2011-11-06 3:18 ` Jeff Kirsher
2011-11-06 19:51 ` Or Gerlitz
2011-11-07 12:46 ` Alexander Kolesen
2011-11-07 16:47 ` Rose, Gregory V [this message]
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=43F901BD926A4E43B106BF17856F075501A1CCA39D@orsmsx508.amr.corp.intel.com \
--to=gregory.v.rose@intel.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=kolesen.a@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=or.gerlitz@gmail.com \
--cc=sibai.li@intel.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).