From: David Miller <davem@davemloft.net>
To: mfuzzey@gmail.com
Cc: richard.rojfors@endian.se, nico@cam.org, netdev@vger.kernel.org
Subject: Re: SMC91x: forcing speed
Date: Mon, 08 Jun 2009 14:44:45 -0700 (PDT) [thread overview]
Message-ID: <20090608.144445.72867560.davem@davemloft.net> (raw)
In-Reply-To: <4A2D85D7.6050509@gmail.com>
From: Martin Fuzzey <mfuzzey@gmail.com>
Date: Mon, 08 Jun 2009 23:42:47 +0200
> IMHO the place for board specific hacks is in the board specifc startup
> code - am I wrong?
We never add bootup time hacks for things that already have
a suitable generic and clean configuration interface.
People ask for module options and all kinds of crap like that
to set link parameters, and we always say no.
next prev parent reply other threads:[~2009-06-08 21:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-04 13:08 SMC91x: forcing speed Martin Fuzzey
2009-06-04 15:02 ` Richard Röjfors
2009-06-08 12:02 ` Martin Fuzzey
2009-06-08 21:22 ` David Miller
2009-06-08 21:42 ` Martin Fuzzey
2009-06-08 21:44 ` David Miller [this message]
2009-06-08 22:17 ` Nicolas Pitre
2009-06-08 23:06 ` David Miller
2009-06-09 1:08 ` Nicolas Pitre
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=20090608.144445.72867560.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=mfuzzey@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nico@cam.org \
--cc=richard.rojfors@endian.se \
/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).