From: "John W. Linville" <linville@tuxdriver.com>
To: Adrian Bunk <bunk@kernel.org>
Cc: Michael Buesch <mb@bu3sch.de>,
Johannes Berg <johannes@sipsolutions.net>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: [RFC: -mm patch] improve the SSB dependencies
Date: Tue, 14 Aug 2007 20:40:35 -0400 [thread overview]
Message-ID: <20070815004035.GL7198@tuxdriver.com> (raw)
In-Reply-To: <20070812224401.GA18945@stusta.de>
On Mon, Aug 13, 2007 at 12:44:02AM +0200, Adrian Bunk wrote:
> On Sun, Aug 12, 2007 at 02:00:26PM +0200, Michael Buesch wrote:
> > Ok, I'll give it a try, with small modifications.
>
> Thanks.
>
> > On Sunday 12 August 2007, Adrian Bunk wrote:
> > > Additional changes in this patch:
> > > - small help text changes
> > > - B44_PCI is no longer usr visible (automatically enabled when possible)
> >
> > I think we want that to be selectable, as it's not needed
> > on some embedded devices. And we need to save memory there.
> >...
>
> Makes sense, but then:
>
> config B44_PCI
> bool "Broadcom 440x PCI device support" if EMBEDDED
> ...
> default y
> ...
>
> I don't care about how many options we present if CONFIG_EMBEDDED=y, but
> for the normal CONFIG_EMBEDDED=n case we should not bother the user with
> this option.
Was all this resolved? Was there another patch? If so, I missed it...
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2007-08-15 1:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-11 0:08 [PATCH] b44-ssb: Fix the SSB dependency hell Michael Buesch
2007-08-11 0:43 ` Adrian Bunk
2007-08-11 0:57 ` Johannes Berg
2007-08-11 1:41 ` Adrian Bunk
2007-08-11 9:36 ` Michael Buesch
2007-08-11 14:30 ` Adrian Bunk
2007-08-11 14:42 ` Michael Buesch
2007-08-11 23:08 ` [RFC: -mm patch] improve the SSB dependencies Adrian Bunk
2007-08-12 12:00 ` Michael Buesch
2007-08-12 22:44 ` Adrian Bunk
2007-08-15 0:40 ` John W. Linville [this message]
2007-08-15 12:47 ` Michael Buesch
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=20070815004035.GL7198@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=mb@bu3sch.de \
--cc=netdev@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 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).