From: Michael Buesch <mb@bu3sch.de>
To: "Mike Frysinger" <vapier.adi@gmail.com>
Cc: "Johannes Berg" <johannes@sipsolutions.net>,
"Mike Frysinger" <vapier@gentoo.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] SSB: make it depend on PCI
Date: Thu, 6 Nov 2008 22:24:26 +0100 [thread overview]
Message-ID: <200811062224.26698.mb@bu3sch.de> (raw)
In-Reply-To: <8bd0f97a0811061314x53e871c8rc9a7de4c4c10f359@mail.gmail.com>
On Thursday 06 November 2008 22:14:30 Mike Frysinger wrote:
> On Thu, Nov 6, 2008 at 11:59, Michael Buesch wrote:
> > On Thursday 06 November 2008 12:32:50 Mike Frysinger wrote:
> >> OK. regarding the patch, if we drop the "&& PCI" part, i think the
> >> rest should get merged ... having empty menus in kconfig is annoying.
> >> agreed ?
> >
> > We have these all over the place.
>
> that's a weak argument. empty menus should go away, not remain
> "because other people are doing it too". with that mentality, there's
> many issues we wouldnt be able to address.
Well, I don't see this as an issue, as 99.9% of the people don't hit that
case and if they do it doesn't matter anyway.
But hey, if you want to apply this, feel free to do so.
--
Greetings Michael.
next prev parent reply other threads:[~2008-11-06 21:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-06 9:51 [PATCH] SSB: make it depend on PCI Mike Frysinger
2008-11-06 11:07 ` Johannes Berg
2008-11-06 11:15 ` Mike Frysinger
2008-11-06 11:22 ` Johannes Berg
2008-11-06 11:26 ` Mike Frysinger
2008-11-06 11:29 ` Johannes Berg
2008-11-06 11:32 ` Mike Frysinger
2008-11-06 11:35 ` Johannes Berg
2008-11-06 16:59 ` Michael Buesch
2008-11-06 21:14 ` Mike Frysinger
2008-11-06 21:24 ` Michael Buesch [this message]
2008-11-06 16:56 ` Michael Buesch
2008-11-09 10:51 ` Geert Uytterhoeven
2008-11-09 11:49 ` Michael Buesch
2008-11-06 16:55 ` 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=200811062224.26698.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vapier.adi@gmail.com \
--cc=vapier@gentoo.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).