From: Russell King <rmk+lkml@arm.linux.org.uk>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Franck <vagabon.xyz@gmail.com>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [NET] Remove ARM dependency for dm9000 driver
Date: Wed, 30 Nov 2005 19:02:24 +0000 [thread overview]
Message-ID: <20051130190224.GE1053@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1133374482.4117.91.camel@baythorne.infradead.org>
On Wed, Nov 30, 2005 at 06:14:42PM +0000, David Woodhouse wrote:
> On Wed, 2005-11-30 at 16:55 +0000, Russell King wrote:
> > So until someone says "I want to use this on such and such arch" I
> > think it's better to keep it dependent on those we know are likely
> > to support it.
>
> I disagree; unless there's a reason why it _shouldn't_ work on a given
> architecture, it should be possible to enable it there.
We agree to disagree. For example, in all probability, ARM will never
see a TPM chip, yet it's offered for selection. Given that, does it
really make sense to offer it for ARM?
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2005-11-30 19:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-30 16:21 [NET] Remove ARM dependency for dm9000 driver Franck
2005-11-30 16:23 ` Russell King
2005-11-30 16:45 ` Franck
2005-11-30 16:55 ` Russell King
2005-11-30 17:07 ` Franck
2005-11-30 18:14 ` David Woodhouse
2005-11-30 19:02 ` Russell King [this message]
2005-12-01 8:36 ` David Woodhouse
2005-12-01 9:41 ` Russell King
2005-12-01 9:51 ` David S. Miller
2005-12-01 10:52 ` Russell King
2005-12-01 11:11 ` Bartlomiej Zolnierkiewicz
2005-12-01 11:37 ` Russell King
2005-12-01 15:20 ` Bartlomiej Zolnierkiewicz
2005-12-01 11:33 ` Christoph Hellwig
2005-11-30 21:48 ` David S. Miller
2005-12-01 7:56 ` Franck
2005-12-01 23:17 ` Matan Ziv-Av
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=20051130190224.GE1053@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vagabon.xyz@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.