From: "John W. Linville" <linville@tuxdriver.com>
To: Dan Williams <dcbw@redhat.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Please pull libertas-2.6
Date: Mon, 11 Jun 2007 16:12:22 -0400 [thread overview]
Message-ID: <20070611201222.GI10397@tuxdriver.com> (raw)
In-Reply-To: <1181396495.23205.0.camel@xo-28-0B-88.localdomain>
On Sat, Jun 09, 2007 at 09:41:35AM -0400, Dan Williams wrote:
> On Tue, 2007-06-05 at 23:55 -0400, Dan Williams wrote:
> > Hi,
> >
> > Changes since you last pulled are mainly Christoph-inspired cleanups, a
> > few bug fixes, mesh scanning, and a few more mesh-specific knobs (though
> > most likely general to 802.11s implementations, not just the CozyBit
> > one).
> >
> > Per the email thread with jgarzik from the last pull, everything from
> > libertas-2.6 'master' branch is currently targeted at _2.6.22_.
>
> Any comments here John?
Sorry, last week was rather busy...
> > Dan Williams (24):
> > libertas: actually remove version.h
> > libertas: kill wlan_scan_process_results
> > libertas: kill ieeetypes_capinfo bitfield, use ieee80211.h types
> > libertas: rename WLAN_802_11_KEY to enc_key and clean up usage
> > libertas: clean up indentation in libertas_association_worker
> > libertas: clean up 802.11 IE post-scan handling
> > libertas: rename private ioctl constants and clean up ioctl handling
> > libertas: remove if_bootcmd.c
> > libertas: fix mixed-case abuse in cmd_ds_802_11_scan
> > libertas: fix mixed-case abuse in cmd_ds_802_11_ad_hoc_result
> > libertas: fix mixed-case abuse in cmd_ds_802_11_ad_hoc_start
> > libertas: re-uppercase command defines and other constants
> > libertas: fix debug build breakage due to field rename
> > libertas: remove thread.h and make kthread usage clearer
> > libertas: new mesh control knobs
> > libertas: bump version to 322.p1
> > libertas: wlan_ -> libertas_ rename in ioctl.c
> > libertas: fix more mixed-case abuse
> > libertas: move generic firmware reset command to common code
> > libertas: wlan_ -> libertas_ function prefix renames for main.c
> > libertas: simplify and clean up data rate handling
> > libertas: fix MESH_[GET/SET]_BCASTR ioctl, clean up ioctl subcmd handling
> > libertas: actually send mesh frames to mesh netdev
> >
> > Luis Carlos Cobo (1):
> > libertas: specific mesh scan for mshX interface
> >
> > Luis Carlos Cobo Rus (2):
> > libertas: pull current channel from firmware on mesh autostart
> > libertas: deauthenticate from AP in channel switch
Jeff had expressed a willingness to accept the previous batch
of libertas patches and pass them to Linus for 2.6.22. However,
judging by the titles above this patch looks more like clean-ups and
new development. Any objection to this batch being targeted at 2.6.23?
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2007-06-11 20:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 3:55 Please pull libertas-2.6 Dan Williams
2007-06-09 13:41 ` Dan Williams
2007-06-11 20:12 ` John W. Linville [this message]
2007-06-11 21:31 ` Dan Williams
2007-06-11 22:13 ` John W. Linville
2007-06-12 3:54 ` Dan Williams
2007-06-12 6:43 ` Holger Schurig
2007-06-12 11:59 ` Dan Williams
2007-06-12 13:19 ` Holger Schurig
2007-06-12 14:05 ` John W. Linville
2007-06-12 15:15 ` Holger Schurig
2007-06-12 15:26 ` Dan Williams
2007-06-12 15:40 ` John W. Linville
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=20070611201222.GI10397@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=dcbw@redhat.com \
--cc=linux-wireless@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).