From: "Rafał Bilski" <rafalbilski@interia.pl>
To: Mark Brown <broonie@sirena.org.uk>
Cc: Tim Hockin <thockin@hockin.org>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: Natsemi DP83815 driver spaming
Date: Thu, 03 May 2007 08:33:17 +0200 [thread overview]
Message-ID: <4639822D.2060302@interia.pl> (raw)
In-Reply-To: <20070502214128.GA4814@sirena.org.uk>
>> What about module option?
>
> That would work, though you crossed in the post with me writing a patch
> adding a sysfs file; I merged the two for overkill (below). I also have
> a patch which changes the log message for the workaround so that it is
> displayed by default in order to make this easier to diagnose.
Applied. I set default value to 0. Flashed. However
> + if (!NATSEMI_CREATE_FILE(pdev, dspcfg_workaround))
> + goto err_create_file;
is going to err_create_file. Without these lines drivers works fine.
Rafał
----------------------------------------------------------------------
NIE KUPUJ!!!
...zanim nie porownasz cen >> http://link.interia.pl/f1a5e
prev parent reply other threads:[~2007-05-03 6:33 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
[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 [this message]
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=4639822D.2060302@interia.pl \
--to=rafalbilski@interia.pl \
--cc=broonie@sirena.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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).