From: Mark Brown <broonie@sirena.org.uk>
To: Tim Hockin <thockin@hockin.org>
Cc: "Rafał Bilski" <rafalbilski@interia.pl>,
"Andrew Morton" <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: Natsemi DP83815 driver spaming
Date: Wed, 2 May 2007 09:22:13 +0100 [thread overview]
Message-ID: <20070502082211.GD31630@sirena.org.uk> (raw)
In-Reply-To: <b3ece790705012351g5c0ff8a6g9f2f350ff86f3319@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 697 bytes --]
On Tue, May 01, 2007 at 11:51:41PM -0700, Tim Hockin wrote:
> 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.
Without a system that really needs the original problem that was being
worked around it's going to be hard to see if the workaround still does
the job. Given the nature of the failure I wouldn't be surprised if it
broke different things on every board that has problems.
How about a sysfs tuneable? It's not nice but at least it's runtime.
--
"You grabbed my hand and we fell into it, like a daydream - or a fever."
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 307 bytes --]
next prev parent reply other threads:[~2007-05-02 8:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <46365887.3010705@interia.pl>
2007-05-01 3:55 ` Natsemi DP83815 driver spaming Andrew Morton
[not found] ` <4636E970.3010602@interia.pl>
[not found] ` <4636F90A.2070303@interia.pl>
2007-05-01 8:35 ` Andrew Morton
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
2007-05-02 8:22 ` Mark Brown [this message]
[not found] ` <b3ece790705020744p2e73bb5fo2c0acad947a5de15@mail.gmail.com>
[not found] ` <4638EF0B.9050701@interia.pl>
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=20070502082211.GD31630@sirena.org.uk \
--to=broonie@sirena.org.uk \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rafalbilski@interia.pl \
--cc=thockin@hockin.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;
as well as URLs for NNTP newsgroup(s).