From: Alan Cox <alan@redhat.com>
To: ionut@moisil.cs.columbia.edu (Ion Badulescu)
Cc: vido@ldh.org, torvalds@transmeta.com, alan@redhat.com,
linux-kernel@vger.kernel.org,
saw@saw.sw.com.sg (Andrey Savochkin)
Subject: Re: [PATCH] eepro100.c, kernel 2.4.1
Date: Thu, 8 Feb 2001 02:42:52 -0500 (EST) [thread overview]
Message-ID: <200102080742.f187gqK01498@devserv.devel.redhat.com> (raw)
In-Reply-To: <200102080723.f187N1v17541@moisil.dev.hydraweb.com> from "Ion Badulescu" at Feb 07, 2001 11:23:01 PM
> It's the printk that gets it wrong, although that's harmless.
> Intel's documentation states that the bug does NOT exist if the
> bits 0 and 1 in eeprom[3] are 1. Thus, the workaround is correct,
> the printk is wrong.
So why does it fix the problem for him. His report and your reply don't
make sense viewed together
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-08 7:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-08 5:53 [PATCH] eepro100.c, kernel 2.4.1 Augustin Vidovic
2001-02-08 7:23 ` Ion Badulescu
2001-02-08 7:37 ` Augustin Vidovic
2001-02-08 7:42 ` Alan Cox [this message]
2001-02-08 7:55 ` Andrey Savochkin
2001-02-08 7:59 ` [PATCH] " Ion Badulescu
2001-02-08 10:41 ` Augustin Vidovic
2001-02-08 11:00 ` Ion Badulescu
2001-02-08 11:15 ` Augustin Vidovic
2001-02-08 11:26 ` Ion Badulescu
2001-02-08 11:44 ` Augustin Vidovic
2001-02-08 11:53 ` Ion Badulescu
2001-02-08 12:08 ` Augustin Vidovic
2001-02-12 5:32 ` Andrey Savochkin
2001-02-12 9:00 ` Ion Badulescu
2001-02-20 6:30 ` Augustin Vidovic
2001-02-20 7:21 ` Andrey Savochkin
2001-02-20 8:18 ` Augustin Vidovic
2001-02-20 23:38 ` Andrey Savochkin
-- strict thread matches above, loose matches on Subject: below --
2001-02-09 14:38 [PATCH] " Peter Lund
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=200102080742.f187gqK01498@devserv.devel.redhat.com \
--to=alan@redhat.com \
--cc=ionut@moisil.cs.columbia.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=saw@saw.sw.com.sg \
--cc=torvalds@transmeta.com \
--cc=vido@ldh.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