From: "John W. Linville" <linville@tuxdriver.com>
To: Tomas Winkler <tomasw@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/2] cfg80211 API for channels/bitrates, mac80211 and driver conversion
Date: Mon, 28 Jan 2008 13:23:47 -0500 [thread overview]
Message-ID: <20080128182347.GG5835@tuxdriver.com> (raw)
In-Reply-To: <1ba2fa240801280823t7a591564pa9129d4799690caf@mail.gmail.com>
On Mon, Jan 28, 2008 at 06:23:53PM +0200, Tomas Winkler wrote:
> On Jan 28, 2008 5:10 PM, John W. Linville <linville@tuxdriver.com> wrote:
> > I think I'm going to hold this back from Dave for 2.6.25. It might
> > be better if we can fix any known problems with this patch before
> > re-merging it for pre-2.6.26 development.
> >
>
> So will you branch it publicly in wireless-2.6 or we do it on mailing
> list? I have some patches for iwl4965 to make HT compile again but
> after Pandora's box has opened so I stopped to try? I will send them
> out.
> What is the window left for 2.6.25? I'm just worried about cfg80211
> general progress.
The development window for 2.6.25 is closed.
The API change will remaind in wireless-2.6 throughout the 2.6.26
development cycle. Please send any fixes for breakage caused by this
patch ASAP.
Thanks,
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2008-01-28 18:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-24 18:38 [PATCH 0/2] the long-awaited bitrate/channel API update Johannes Berg
2008-01-24 18:38 ` [PATCH 1/2] cfg80211 API for channels/bitrates, mac80211 and driver conversion Johannes Berg
2008-01-28 0:49 ` Tomas Winkler
2008-01-28 15:10 ` John W. Linville
2008-01-28 16:23 ` Tomas Winkler
2008-01-28 18:23 ` John W. Linville [this message]
2008-01-29 14:05 ` Johannes Berg
2008-01-29 15:04 ` Tomas Winkler
2008-01-24 18:38 ` [PATCH 2/2] nl80211: export hardware bitrate/channel capabilities 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=20080128182347.GG5835@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=tomasw@gmail.com \
/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.