From: Roopa Prabhu <roprabhu@cisco.com>
To: Roopa Prabhu <roprabhu@cisco.com>,
Randy Dunlap <rdunlap@xenotime.net>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: <linux-next@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>,
Netdev <netdev@vger.kernel.org>,
"Christian Benvenuti (benve)" <benve@cisco.com>
Subject: Re: linux-next: Tree for Jan 19 (cisco/enic)
Date: Thu, 19 Jan 2012 21:45:22 -0800 [thread overview]
Message-ID: <CB3E3F72.412F2%roprabhu@cisco.com> (raw)
In-Reply-To: <CB3E3CB9.412EA%roprabhu@cisco.com>
On 1/19/12 9:33 PM, "Roopa Prabhu" <roprabhu@cisco.com> wrote:
>
>
>
> On 1/19/12 3:43 PM, "Randy Dunlap" <rdunlap@xenotime.net> wrote:
>
>> On 01/18/2012 05:59 PM, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Changes since 20120118:
>>
>>
>> on x86_64:
>>
>> /next/linux-next-20120119/drivers/net/ethernet/cisco/enic/enic_main.c: In
>> function 'enic_probe':
>>
/next/linux-next-20120119/drivers/net/ethernet/cisco/enic/enic_main.c:2387:16>>
:
>> error: 'struct enic' has no member named 'num_vfs'
>>
/next/linux-next-20120119/drivers/net/ethernet/cisco/enic/enic_main.c:2387:32>>
:
>> error: 'struct enic' has no member named 'num_vfs'
>>
>>
>> Full randconfig file is attached.
>>
>> --
>> ~Randy
>> *** Remember to use Documentation/SubmitChecklist when testing your code ***
>>
> Thanks for reporting stephen. Its because you don't have CONFIG_PCI_IOV
> enabled. I will working on the patch. Will submit soon.
>
Actually thanks randy. Patch coming soon..
>
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2012-01-20 5:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 1:59 linux-next: Tree for Jan 19 Stephen Rothwell
2012-01-19 3:07 ` linux-next: Tree for Jan 19 (uml) Randy Dunlap
2012-01-19 2:18 ` Stephen Rothwell
2012-01-19 3:40 ` Linus Torvalds
2012-01-19 22:27 ` linux-next: Tree for Jan 19 (block/nvme) Randy Dunlap
2012-01-19 22:35 ` linux-next: Tree for Jan 19 (mm/memcontrol.c) Randy Dunlap
2012-01-20 0:00 ` KAMEZAWA Hiroyuki
2012-01-20 11:09 ` Glauber Costa
2012-01-19 23:43 ` linux-next: Tree for Jan 19 (cisco/enic) Randy Dunlap
2012-01-20 5:33 ` Roopa Prabhu
2012-01-20 5:45 ` Roopa Prabhu [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=CB3E3F72.412F2%roprabhu@cisco.com \
--to=roprabhu@cisco.com \
--cc=benve@cisco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=sfr@canb.auug.org.au \
/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