linux-kernel - Re: e1000 oops on boot [Re: 2.6.21-rc2-mm2]

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 7 Mar 2007 16:28:53 -0800
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	=?ISO-8859-1?Q? "J.A._Magall=F3n" ?= <jamagallon@....com>,
	linux-kernel@...r.kernel.org, Auke Kok <auke-jan.h.kok@...el.com>
Subject: Re: e1000 oops on boot [Re: 2.6.21-rc2-mm2]

On Wed, 7 Mar 2007 16:23:15 -0800 Andrew Morton wrote:

> The below will apppear in -rc3-mm1 (hopefully later today) and it will
> hopefully fix that crash.
> 
> 
> From: Auke Kok <auke-jan.h.kok@...el.com>
> 
> ---
> 
>  drivers/net/e1000/e1000_main.c |   66 +++++++++++++++++++++----------
>  1 files changed, 45 insertions(+), 21 deletions(-)
> 
> diff -puN drivers/net/e1000/e1000_main.c~e1000-fix-be-ready-for-incoming-irq-at-pci_request_irq drivers/net/e1000/e1000_main.c
> --- a/drivers/net/e1000/e1000_main.c~e1000-fix-be-ready-for-incoming-irq-at-pci_request_irq
> +++ a/drivers/net/e1000/e1000_main.c
> @@ -522,14 +522,15 @@ e1000_release_manageability(struct e1000
>  	}
>  }

Auke:

Below, please s/@...pter =/@...pter:/ to make it be correct
kernel-doc notation.

> -int
> -e1000_up(struct e1000_adapter *adapter)
> +/**
> + * e1000_configure - configure the hardware for RX and TX
> + * @adapter = private board structure
> + **/
> +static void e1000_configure(struct e1000_adapter *adapter)
>  {


---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/