From: Jeff Garzik <jeff@garzik•org>
To: Andrew Morton <akpm@linux-foundation•org>
Cc: davem@davemloft•net, netdev@vger•kernel.org,
michael.pyne@kdemail•net, AAbdulla@nvidia•com, stable@kernel•org
Subject: Re: [patch 1/4] forcedeth: fix MAC address detection on network card (regression in 2.6.23)
Date: Fri, 09 Jan 2009 17:04:47 -0500 [thread overview]
Message-ID: <4967C9FF.6020504@garzik.org> (raw)
In-Reply-To: <20090109133749.59c20e40.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Fri, 09 Jan 2009 16:23:38 -0500
> Jeff Garzik <jeff@garzik•org> wrote:
>
>>> On Tue, 05 Feb 2008 13:20:59 -0500 Jeff Garzik <jeff@garzik•org> wrote:
>>>> NAK - this fixes one set of users, and breaks a working set of users.
>>>>
>>>> Need to add DMI check for the specific motherboard (dmi_check_system),
>>>> and flip flag according to success/failure of that check.
>>> Signed-off-by: Andrew Morton <akpm@linux-foundation•org>
>> I'll just highlight this quoted bit for David...
>>
>> I've already posted a dmi_check_system() solution too
>
> What is the status of that? Where is it?
You were CC'd on it each time... Here's a copy from the archives:
http://www.mail-archive.com/netdev@vger.kernel.org/msg61096.html
>> -- you just need
>> to fill in the motherboard details to fix the regression while keeping
>> others' systems working.
>
> Can you please tell Michael what info is needed to wrap this up? And
> how he is to obtain it?
I think he posted dmidecode output.
I also think he said a BIOS update fixed the problem, at least according
to the mail thread.
Jeff
next prev parent reply other threads:[~2009-01-09 22:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-09 20:23 [patch 1/4] forcedeth: fix MAC address detection on network card (regression in 2.6.23) akpm
2009-01-09 21:23 ` Jeff Garzik
2009-01-09 21:37 ` Andrew Morton
2009-01-09 22:04 ` Jeff Garzik [this message]
2009-01-10 7:10 ` David Miller
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=4967C9FF.6020504@garzik.org \
--to=jeff@garzik$(echo .)org \
--cc=AAbdulla@nvidia$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=michael.pyne@kdemail$(echo .)net \
--cc=netdev@vger$(echo .)kernel.org \
--cc=stable@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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