public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jeff V. Merkey" <jmerkey@wolfmountaingroup.com>
To: "Kok, Auke" <auke-jan.h.kok@intel.com>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Latest e1000 7.3.20 driver busted with 2.6.20.4
Date: Wed, 04 Apr 2007 13:46:41 -0600	[thread overview]
Message-ID: <461400A1.7080907@wolfmountaingroup.com> (raw)
In-Reply-To: <4613FD2C.101@intel.com>

Kok, Auke wrote:

> Jeff V. Merkey wrote:
>
>> CC [M]  drivers/net/chelsio/mv88x201x.o
>>   CC [M]  drivers/net/chelsio/my3126.o
>>   LD [M]  drivers/net/chelsio/cxgb.o
>>   CC      drivers/net/e1000/e1000_main.o
>> drivers/net/e1000/e1000_main.c:1185:45: error: macro "INIT_WORK" 
>> passed 3 arguments, but takes just 2
>> ared (first use in this function)
>> drivers/net/e1000/e1000_main.c:1184: error: (Each undeclared 
>> identifier is reported only once
>> drivers/net/e1000/e1000_main.c:1184: error: for each function it 
>> appears in.)
>> make[3]: *** [drivers/net/e1000/e1000_main.o] Error 1
>> make[2]: *** [drivers/net/e1000] Error 2
>> make[1]: *** [drivers/net] Error 2
>> make: *** [drivers] Error 2
>
>
> this is hardly a thread for lkml as you're posting about out 
> out-of-tree driver.  This issue has also been fixed in 7.4.35 which 
> was released last week on e1000.sf.net. In the future, please post 
> this stuff to e1000-devel@lists.sourceforge.net where we discuss the 
> out-of-tree driver.
>
> Cheers,
>
> Auke
>
Thanks.  I'll download Intel's latest driver and test it.   I wasn't 
discussing the out of tree driver (why do you have a broken Linux out of 
tree driver, BTW?   If its for Linux, shouldn't it be updated here 
first) but the driver in 2.6.20.4 (which is missing support four 
additional chipsets). 

Jeff

  reply	other threads:[~2007-04-04 19:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-04 17:36 Latest e1000 7.3.20 driver busted with 2.6.20.4 Jeff V. Merkey
2007-04-04 19:31 ` Kok, Auke
2007-04-04 19:46   ` Jeff V. Merkey [this message]
2007-04-04 19:54     ` Kok, Auke
2007-04-04 20:12       ` Jeff V. Merkey

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=461400A1.7080907@wolfmountaingroup.com \
    --to=jmerkey@wolfmountaingroup.com \
    --cc=auke-jan.h.kok@intel.com \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox