From: Dave Jones <davej@redhat.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: dell_rbu driver depends on x86[64]
Date: Sat, 19 Nov 2005 01:23:32 -0500 [thread overview]
Message-ID: <20051119062332.GB7335@redhat.com> (raw)
In-Reply-To: <20051118221744.2aa58499.akpm@osdl.org>
On Fri, Nov 18, 2005 at 10:17:44PM -0800, Andrew Morton wrote:
> Dave Jones <davej@redhat.com> wrote:
> >
> > On Fri, Nov 18, 2005 at 10:01:44PM -0800, Andrew Morton wrote:
> > > Dave Jones <davej@redhat.com> wrote:
> > > >
> > > > This driver only appears on IA32 & EM64T boxes.
> > > >
> > > > Signed-off-by: Dave Jones <davej@redhat.com>
> > > >
> > > > --- linux-2.6.14/drivers/firmware/Kconfig~ 2005-11-14 19:23:45.000000000 -0500
> > > > +++ linux-2.6.14/drivers/firmware/Kconfig 2005-11-14 19:24:18.000000000 -0500
> > > > @@ -60,6 +60,7 @@ config EFI_PCDP
> > > >
> > > > config DELL_RBU
> > > > tristate "BIOS update support for DELL systems via sysfs"
> > > > + depends on X86
> > > > select FW_LOADER
> > > > help
> > > > Say m if you want to have the option of updating the BIOS for your
> > >
> > > Does it not compile on other architectures? If it does, there's an
> > > argument for leaving it there, for compile coverage.
> >
> > If this were a "only works on non-x86" driver, I'd agree, but
> > x86 drivers probably get way more coverage than any arch already,
> > so I don't we really gain much by having this available on
> > archs that can't run it.
>
> Where's the advantage in removing it from non-x86 builds?
One less pointless option showing up in configs.
Just like we don't have countless other arch-specific drivers showing
up under non-native archs. Why is this one different ?
Dave
prev parent reply other threads:[~2005-11-19 6:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-18 21:29 dell_rbu driver depends on x86[64] Dave Jones
2005-11-19 6:01 ` Andrew Morton
2005-11-19 6:14 ` Dave Jones
2005-11-19 6:17 ` Andrew Morton
2005-11-19 6:23 ` Dave Jones [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=20051119062332.GB7335@redhat.com \
--to=davej@redhat.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.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 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.