From: John Fastabend <john.r.fastabend@intel.com>
To: divya <dipraksh@linux.vnet.ibm.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
netdev <netdev@vger.kernel.org>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>
Subject: Re: build failure
Date: Thu, 05 Aug 2010 09:48:01 -0700 [thread overview]
Message-ID: <4C5AEB41.9050903@intel.com> (raw)
In-Reply-To: <4C5A4CF4.4070203@linux.vnet.ibm.com>
divya wrote:
> Yestersday's linux-next(2.6.35_next_20100802) build fails with the following error on both system p and x.
>
>
> drivers/net/ixgbe/ixgbe_main.c: In function 'ixgbe_select_queue':
> drivers/net/ixgbe/ixgbe_main.c:6159: error: 'struct ixgbe_fcoe' has no member named 'up'
> drivers/net/ixgbe/ixgbe_main.c: In function 'ixgbe_xmit_frame':
> drivers/net/ixgbe/ixgbe_main.c:6221: error: 'struct ixgbe_fcoe' has no member named 'up'
> make[3]: *** [drivers/net/ixgbe/ixgbe_main.o] Error 1
> make[2]: *** [drivers/net/ixgbe] Error 2
> make[2]: *** Waiting for unfinished jobs....
> make[1]: *** [drivers/net] Error 2
> make: *** [drivers] Error 2
>
> Thanks
> Divya
>
>
Hi Divya,
Jeff should have a fix for this in his queue already. This is caused by
building with CONFIG_FCOE and without CONFIG_IXGBE_DCB.
Thanks,
John.
WARNING: multiple messages have this Message-ID (diff)
From: John Fastabend <john.r.fastabend@intel.com>
To: divya <dipraksh@linux.vnet.ibm.com>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
netdev <netdev@vger.kernel.org>
Subject: Re: [linux-next] build failure
Date: Thu, 05 Aug 2010 09:48:01 -0700 [thread overview]
Message-ID: <4C5AEB41.9050903@intel.com> (raw)
In-Reply-To: <4C5A4CF4.4070203@linux.vnet.ibm.com>
divya wrote:
> Yestersday's linux-next(2.6.35_next_20100802) build fails with the following error on both system p and x.
>
>
> drivers/net/ixgbe/ixgbe_main.c: In function 'ixgbe_select_queue':
> drivers/net/ixgbe/ixgbe_main.c:6159: error: 'struct ixgbe_fcoe' has no member named 'up'
> drivers/net/ixgbe/ixgbe_main.c: In function 'ixgbe_xmit_frame':
> drivers/net/ixgbe/ixgbe_main.c:6221: error: 'struct ixgbe_fcoe' has no member named 'up'
> make[3]: *** [drivers/net/ixgbe/ixgbe_main.o] Error 1
> make[2]: *** [drivers/net/ixgbe] Error 2
> make[2]: *** Waiting for unfinished jobs....
> make[1]: *** [drivers/net] Error 2
> make: *** [drivers] Error 2
>
> Thanks
> Divya
>
>
Hi Divya,
Jeff should have a fix for this in his queue already. This is caused by
building with CONFIG_FCOE and without CONFIG_IXGBE_DCB.
Thanks,
John.
WARNING: multiple messages have this Message-ID (diff)
From: John Fastabend <john.r.fastabend@intel.com>
To: divya <dipraksh@linux.vnet.ibm.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
netdev <netdev@vger.kernel.org>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>
Subject: Re: [linux-next] build failure
Date: Thu, 05 Aug 2010 09:48:01 -0700 [thread overview]
Message-ID: <4C5AEB41.9050903@intel.com> (raw)
In-Reply-To: <4C5A4CF4.4070203@linux.vnet.ibm.com>
divya wrote:
> Yestersday's linux-next(2.6.35_next_20100802) build fails with the following error on both system p and x.
>
>
> drivers/net/ixgbe/ixgbe_main.c: In function 'ixgbe_select_queue':
> drivers/net/ixgbe/ixgbe_main.c:6159: error: 'struct ixgbe_fcoe' has no member named 'up'
> drivers/net/ixgbe/ixgbe_main.c: In function 'ixgbe_xmit_frame':
> drivers/net/ixgbe/ixgbe_main.c:6221: error: 'struct ixgbe_fcoe' has no member named 'up'
> make[3]: *** [drivers/net/ixgbe/ixgbe_main.o] Error 1
> make[2]: *** [drivers/net/ixgbe] Error 2
> make[2]: *** Waiting for unfinished jobs....
> make[1]: *** [drivers/net] Error 2
> make: *** [drivers] Error 2
>
> Thanks
> Divya
>
>
Hi Divya,
Jeff should have a fix for this in his queue already. This is caused by
building with CONFIG_FCOE and without CONFIG_IXGBE_DCB.
Thanks,
John.
next prev parent reply other threads:[~2010-08-05 16:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-05 5:32 [linux-next] build failure divya
2010-08-05 16:48 ` John Fastabend [this message]
2010-08-05 16:48 ` John Fastabend
2010-08-05 16:48 ` John Fastabend
-- strict thread matches above, loose matches on Subject: below --
2012-11-14 9:15 Build failure Andreas Müller
2012-11-14 9:30 ` Andreas Müller
[not found] <BANLkTikBm0gmNd8oQ6CN+cAEbYhWEGvWPA@mail.gmail.com>
2011-04-30 14:31 ` Build Failure Colin Minihan
2011-04-30 16:10 ` Andy Walls
2011-05-01 1:28 ` Mauro Carvalho Chehab
2011-05-01 11:50 ` Vincent McIntyre
2011-01-24 21:36 Build failure Gary Thomas
2011-01-24 21:52 ` Tom Zanussi
2011-01-24 23:05 ` Gary Thomas
2011-01-25 0:00 ` Tian, Kevin
2011-01-25 22:51 ` Richard Purdie
2009-02-18 22:42 jonr
2009-02-18 23:47 ` Jeremy Fitzhardinge
2009-02-19 0:50 ` jonr
2008-07-30 9:29 build failure Christoph Egger
2008-07-30 9:49 ` Keir Fraser
2008-07-30 11:01 ` Christoph Egger
2007-06-08 10:24 Build failure Steinar H. Gunderson
2007-06-08 10:47 ` Steinar H. Gunderson
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=4C5AEB41.9050903@intel.com \
--to=john.r.fastabend@intel.com \
--cc=dipraksh@linux.vnet.ibm.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.