From: Johannes Berg <johannes@sipsolutions.net>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-wireless <linux-wireless@vger.kernel.org>,
b43-dev@lists.infradead.org
Subject: linux-next: Tree for May 6 (b43/bcma)
Date: Tue, 07 May 2013 11:15:36 +0200 [thread overview]
Message-ID: <1367918136.8328.1.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <51886FAF.1030801@lwfinger.net> (sfid-20130507_051212_785834_D4BC17E9)
On Mon, 2013-05-06 at 22:06 -0500, Larry Finger wrote:
> > Probably mostly due to B43=y and BCMA=m.
>
> Does any Kconfig wizard know the magic incantation to accomplish the following:
>
> 1. Ensure that if SSB and BMCA are both selected, then both are either "m" or "y"
I think one of them being m and the other y should be OK? But do they
have interdependencies?
> 2. Ensure that BRCMSMAC is not "y" if BMCA is "m".
Isn't that a simple
depends on BCMA
or maybe it can work w/o BCMA, then you'd have
depends on BCMA || !BCMA
> 3. Ensure that B43 is not "y" if SSB and/or BCMA is "m".
same.
johannes
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Berg <johannes@sipsolutions.net>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-wireless <linux-wireless@vger.kernel.org>,
b43-dev@lists.infradead.org
Subject: Re: linux-next: Tree for May 6 (b43/bcma)
Date: Tue, 07 May 2013 11:15:36 +0200 [thread overview]
Message-ID: <1367918136.8328.1.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <51886FAF.1030801@lwfinger.net> (sfid-20130507_051212_785834_D4BC17E9)
On Mon, 2013-05-06 at 22:06 -0500, Larry Finger wrote:
> > Probably mostly due to B43=y and BCMA=m.
>
> Does any Kconfig wizard know the magic incantation to accomplish the following:
>
> 1. Ensure that if SSB and BMCA are both selected, then both are either "m" or "y"
I think one of them being m and the other y should be OK? But do they
have interdependencies?
> 2. Ensure that BRCMSMAC is not "y" if BMCA is "m".
Isn't that a simple
depends on BCMA
or maybe it can work w/o BCMA, then you'd have
depends on BCMA || !BCMA
> 3. Ensure that B43 is not "y" if SSB and/or BCMA is "m".
same.
johannes
next prev parent reply other threads:[~2013-05-07 9:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-06 4:42 linux-next: Tree for May 6 Stephen Rothwell
2013-05-06 4:42 ` Stephen Rothwell
2013-05-06 16:14 ` linux-next: Tree for May 6 (lpfc) Randy Dunlap
2013-05-06 16:49 ` James Bottomley
2013-05-06 17:36 ` Martin K. Petersen
2013-05-06 17:48 ` Randy Dunlap
2013-05-06 17:42 ` linux-next: Tree for May 6 (b43/bcma) Randy Dunlap
2013-05-06 17:42 ` Randy Dunlap
2013-05-07 3:06 ` Larry Finger
2013-05-07 3:06 ` Larry Finger
2013-05-07 3:06 ` Larry Finger
2013-05-07 9:15 ` Johannes Berg [this message]
2013-05-07 9:15 ` Johannes Berg
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=1367918136.8328.1.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=Larry.Finger@lwfinger.net \
--cc=b43-dev@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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.