From: "Tim Hockin" <thockin@hockin.org>
To: "Rafał Bilski" <rafalbilski@interia.pl>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: Natsemi DP83815 driver spaming
Date: Tue, 1 May 2007 23:51:41 -0700 [thread overview]
Message-ID: <b3ece790705012351g5c0ff8a6g9f2f350ff86f3319@mail.gmail.com> (raw)
In-Reply-To: <463830E1.8080107@interia.pl>
On 5/1/07, Rafal Bilski <rafalbilski@interia.pl> wrote:
> 2.6.21.1 is first kernel which I'm using at this device. Earlier it was
> WindowsCE terminal. It is hardware fault. Commenting out the code is my
> way to avoid "wakeup" messages in log, but I don't want to change anything
> in vanilla kernel. I'm lucky that NIC is working at all.
I'm not sure what the right answer is. The code was designed to do
the right thing, and yet in your case it's broken. Does it need to be
a build option to work around broken hardware? Yuck.
next prev parent reply other threads:[~2007-05-02 6:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-30 20:58 Rafał Bilski
2007-05-01 3:55 ` Andrew Morton
2007-05-01 7:17 ` Rafał Bilski
2007-05-01 8:23 ` Rafał Bilski
2007-05-01 8:35 ` Andrew Morton
2007-05-01 10:40 ` Rafał Bilski
2007-05-01 8:46 ` Mark Brown
2007-05-01 10:25 ` Rafał Bilski
2007-05-01 18:08 ` Mark Brown
2007-05-01 19:10 ` Rafał Bilski
2007-05-01 19:52 ` Rafał Bilski
2007-05-01 21:27 ` Mark Brown
[not found] ` <b3ece790705011543gdca3a9ei905d3499b6c18dc8@mail.gmail.com>
2007-05-02 5:54 ` Rafał Bilski
[not found] ` <b3ece790705012303x1e5a2d03xddf6c14aec5a99d8@mail.gmail.com>
2007-05-02 6:34 ` Rafał Bilski
2007-05-02 6:51 ` Tim Hockin [this message]
2007-05-02 8:22 ` Mark Brown
[not found] ` <b3ece790705020744p2e73bb5fo2c0acad947a5de15@mail.gmail.com>
2007-05-02 20:05 ` Rafał Bilski
2007-05-02 20:48 ` Tim Hockin
2007-05-02 21:41 ` Mark Brown
2007-05-03 6:33 ` Rafał Bilski
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=b3ece790705012351g5c0ff8a6g9f2f350ff86f3319@mail.gmail.com \
--to=thockin@hockin.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rafalbilski@interia.pl \
/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
all inboxes | Powered by JetHome®