From: Jeff Garzik <jeff-o2qLIJkoznsdnm+yROfE0A@public.gmane.org>
To: "John W. Linville" <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
Cc: linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Dan Williams <dcbw-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: Please pull 'libertas-fixes' branch of wireless-2.6
Date: Tue, 12 Jun 2007 18:54:35 -0400 [thread overview]
Message-ID: <466F242B.1030900@garzik.org> (raw)
In-Reply-To: <20070612210658.GG310-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
John W. Linville wrote:
> Fixes identified by the libertas team as important for 2.6.22...
>
> ---
>
> The following changes since commit 717c9339202a42ae7bec7d3c4b84deecdcae9f81:
> Dan Williams (1):
> libertas: reduce SSID and BSSID mixed-case abuse
>
> are found in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-2.6.git libertas-fixes
>
> Dan Williams (1):
> libertas: actually send mesh frames to mesh netdev
>
> Luis Carlos (1):
> libertas: convert libertas_mpp into anycast_mask
>
> Luis Carlos Cobo Rus (2):
> libertas: pull current channel from firmware on mesh autostart
> libertas: deauthenticate from AP in channel switch
Just to be clear, you intend 'libertas' and 'libertas-fixes' (in that
order) for 2.6.22, and 'libertas-upstream' for 2.6.23?
Jeff
next prev parent reply other threads:[~2007-06-12 22:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-29 18:33 Please pull 'libertas' branch of wireless-2.6 John W. Linville
[not found] ` <20070529183347.GD3496-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-05-30 14:07 ` Jeff Garzik
2007-05-30 15:28 ` Dan Williams
[not found] ` <1180538928.17163.10.camel-Hs+VJEcF3DojzQS9c19i8iZi+YwRKgec@public.gmane.org>
2007-05-31 21:13 ` Dan Williams
2007-05-31 21:16 ` John W. Linville
[not found] ` <20070531211605.GA30161-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-06-01 21:48 ` Dan Williams
2007-06-12 21:05 ` John W. Linville
2007-06-12 21:06 ` Please pull 'libertas-fixes' " John W. Linville
[not found] ` <20070612210658.GG310-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-06-12 21:08 ` Please pull 'libertas-upstream' " John W. Linville
[not found] ` <20070612210814.GH310-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-06-13 19:57 ` Jeff Garzik
2007-06-12 22:54 ` Jeff Garzik [this message]
2007-06-13 0:03 ` Please pull 'libertas-fixes' " John W. Linville
2007-06-13 2:28 ` Jeff Garzik
[not found] ` <20070612210544.GF310-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-06-12 21:26 ` Please pull 'libertas' branch of wireless-2.6 (resent w/o attachment) John W. Linville
2007-06-13 2:28 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2007-06-27 20:55 Please pull 'libertas-fixes' branch of wireless-2.6 John W. Linville
[not found] ` <20070627205539.GB13617-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-07-02 11:07 ` Dan Williams
2007-07-02 12:14 ` Jeff Garzik
2007-07-03 18:48 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=466F242B.1030900@garzik.org \
--to=jeff-o2qlijkoznsdnm+yrofe0a@public.gmane.org \
--cc=dcbw-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).