From: "John W. Linville" <linville@tuxdriver.com>
To: Ivo Van Doorn <ivdoorn@gmail.com>
Cc: Jiri Benc <jbenc@suse.cz>, Christoph Hellwig <hch@infradead.org>,
Michael Wu <flamingice@sourmilk.net>,
netdev@vger.kernel.org
Subject: Re: [PATCH dscape] d80211: Switch d80211.h to IEEE80211_ style names
Date: Tue, 1 Aug 2006 13:11:04 -0400 [thread overview]
Message-ID: <20060801171058.GH29208@tuxdriver.com> (raw)
In-Reply-To: <a32f33a40608010725m247304a5vda49207c8f36cf62@mail.gmail.com>
On Tue, Aug 01, 2006 at 04:25:05PM +0200, Ivo Van Doorn wrote:
> Hi,
>
> >> Do you have a plan when you will merge rt2x00 patches so I can apply
> >> Michael's renaming patch(es) without risk of conflicts?
> >
> >Working on it ~now. I hit a snag in that Ivo's patches seem to rely on
> >his radio button patch, which I had ignored until now. I'll probably
> >pull that in this morning (or figure-out how to not need it) and get
> >something pushed to wireless-dev sometime today.
>
> Ehm, that should not have happened. The rt2x00 version I had send as patches
> had the radio button integrated as they had been in wireless-dev already.
> The patch to convert it to the rfkill driver is one of the patches
> I'll send later.
The rfkill stuff seems to be behind a CONFIG_RT2X00_BUTTON define,
which keys off some driver-specific Kconfig stuff. They were
getting turned-on by default w/ 'allmodconfig' and 'allyesconfig'.
Turning them off in .config lets them compile.
In general, I'd prefer not to have Kconfig-settable options that
don't compile. But in this case I guess we'll just live with it.
After all, it is a development tree... :-)
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2006-08-01 17:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-27 7:37 [PATCH dscape] d80211: Switch d80211.h to IEEE80211_ style names Michael Wu
2006-07-31 20:31 ` John W. Linville
2006-07-31 20:51 ` Michael Wu
2006-08-01 9:56 ` Christoph Hellwig
2006-08-01 12:21 ` John W. Linville
2006-08-01 13:58 ` Jiri Benc
2006-08-01 14:07 ` John W. Linville
2006-08-01 14:25 ` Ivo Van Doorn
2006-08-01 17:11 ` John W. Linville [this message]
2006-08-01 17:31 ` Ivo van Doorn
2006-08-01 19:13 ` Ulrich Kunitz
2006-08-05 11:46 ` Christoph Hellwig
2006-08-05 17:30 ` Michael Buesch
2006-08-05 17:47 ` Michael Buesch
-- strict thread matches above, loose matches on Subject: below --
2006-07-25 6:02 Michael Wu
2006-07-26 16:32 ` Jiri Benc
2006-07-26 16:43 ` Michael Wu
2006-07-26 16:53 ` Jiri Benc
2006-07-26 17:10 ` Michael Wu
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=20060801171058.GH29208@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=flamingice@sourmilk.net \
--cc=hch@infradead.org \
--cc=ivdoorn@gmail.com \
--cc=jbenc@suse.cz \
--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).