From: Mike Frysinger <vapier.adi@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: Steve.Glendinning@smsc.com, netdev@vger.kernel.org,
Ian.Saturley@smsc.com, uclinux-dist-devel@blackfin.uclinux.org
Subject: Re: [Uclinux-dist-devel] [PATCH 1/2] netdev: smsc911x: allow building on Blackfin systems
Date: Mon, 8 Jun 2009 17:50:32 -0400 [thread overview]
Message-ID: <8bd0f97a0906081450s6b471d30p56d86e31ba708730@mail.gmail.com> (raw)
In-Reply-To: <20090608.143710.83724675.davem@davemloft.net>
On Mon, Jun 8, 2009 at 17:37, David Miller wrote:
> From: Steve.Glendinning@smsc.com
>> You're right, there's nothing "special" about ARM | SUPERH other than they
>> cover all the in-tree platforms using smsc911x. The aim was to hide this
>> option from menuconfig on x86 etc, where this device is extremely unlikely
>> to be found. Maybe there's a better way of doing this?
>
> I sincerely doubt keeping this out of x86's menuconfig so important,
> really.
and desktop systems' menuconfig is so big that i dont think one more
driver will make a difference
> So many devices are available for powerpc and sparc64 that will never
> appear there, however those drivers now get build validated on those
> platforms and it's therefore a net-win.
i run randconfigs nightly ... it's neat the kind of unlikely build bugs you find
-mike
next prev parent reply other threads:[~2009-06-08 21:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-06 0:37 [PATCH 1/2] netdev: smsc911x: allow building on Blackfin systems Mike Frysinger
2009-06-06 0:37 ` [PATCH 2/2] netdev: smsc911x: add missing __devexit_p() usage Mike Frysinger
2009-06-08 7:10 ` David Miller
[not found] ` <1244248640-22699-2-git-send-email-vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2009-06-08 19:37 ` Steve.Glendinning-sdUf+H5yV5I
2009-06-08 7:10 ` [PATCH 1/2] netdev: smsc911x: allow building on Blackfin systems David Miller
2009-06-08 19:36 ` Steve.Glendinning
2009-06-08 21:29 ` [Uclinux-dist-devel] [PATCH 1/2] netdev: smsc911x: allowbuilding " Hennerich, Michael
2009-06-08 21:37 ` [PATCH 1/2] netdev: smsc911x: allow building " David Miller
2009-06-08 21:50 ` Mike Frysinger [this message]
[not found] ` <8bd0f97a0906081450s6b471d30p56d86e31ba708730-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-06-09 8:04 ` Steve.Glendinning-sdUf+H5yV5I
2009-06-09 8:22 ` [PATCH 1/2 v2] netdev: smsc911x: allow building on any system Mike Frysinger
2009-06-09 8:37 ` David Miller
2009-06-09 9:13 ` [PATCH 1/2 v3] " Mike Frysinger
2009-06-09 10:59 ` David Miller
2009-06-09 11:08 ` [Uclinux-dist-devel] " Mike Frysinger
2009-06-09 12:21 ` David Miller
2009-06-09 12:23 ` David Miller
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=8bd0f97a0906081450s6b471d30p56d86e31ba708730@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=Ian.Saturley@smsc.com \
--cc=Steve.Glendinning@smsc.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=uclinux-dist-devel@blackfin.uclinux.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