All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: Please pull 'fixes-jgarzik' branch of wireless-2.6
Date: Mon, 29 Oct 2007 05:48:14 -0400	[thread overview]
Message-ID: <4725AC5E.3080006@garzik.org> (raw)
In-Reply-To: <20071026030826.GB14080@tuxdriver.com>

John W. Linville wrote:
> Jeff,
> 
> A few fixes for 2.6.24...
> 
> Thanks,
> 
> John
> 
> ---
> 
> Individual patches available here:
> 
> 	http://www.kernel.org/pub/linux/kernel/people/linville/wireless-2.6/fixes-jgarzik
> 
> ---
> 
> The following changes since commit c9927c2bf4f45bb85e8b502ab3fb79ad6483c244:
>   Linus Torvalds (1):
>         Linux 2.6.24-rc1
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-2.6.git fixes-jgarzik
> 
> Anton Blanchard (3):
>       ipw2100/ipw2200: jiffies_round -> jiffies_round_relative
>       rt2x00: jiffies_round -> jiffies_round_relative
>       b43/b43legacy: jiffies_round -> jiffies_round_relative
> 
> Michael Wu (1):
>       rtl8187: Allow multicast frames
> 
> Mohamed Abbas (3):
>       iwl4965: fix scan problem
>       iwl3945: cancel scan on rxon command
>       iwl3945: fix direct scan problem
> 
> Tomas Winkler (1):
>       iwlwifi: fix sending probe request in iwl 4965
> 
> mabbas (1):
>       iwl4965: fix driver hang related to hardware scan
> 
>  drivers/net/wireless/b43/main.c             |    2 +-
>  drivers/net/wireless/b43legacy/main.c       |    2 +-
>  drivers/net/wireless/ipw2100.c              |   11 +++--
>  drivers/net/wireless/ipw2200.c              |    6 +-
>  drivers/net/wireless/iwlwifi/iwl-4965.c     |    6 +--
>  drivers/net/wireless/iwlwifi/iwl3945-base.c |   56 +++++++++++++++++++++++----
>  drivers/net/wireless/iwlwifi/iwl4965-base.c |   56 +++++++++++++++++++++++----
>  drivers/net/wireless/rt2x00/rt2x00lib.h     |    2 +-
>  drivers/net/wireless/rtl8187_dev.c          |   20 +++++----
>  9 files changed, 121 insertions(+), 40 deletions(-)

pulled



  reply	other threads:[~2007-10-29  9:48 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-26  3:08 Please pull 'fixes-jgarzik' branch of wireless-2.6 John W. Linville
2007-10-29  9:48 ` Jeff Garzik [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-01-16 21:27 John W. Linville
2008-01-18 19:40 ` Jeff Garzik
2008-01-10 19:49 John W. Linville
2008-01-10 20:57 ` John W. Linville
2008-01-08  5:15 John W. Linville
2008-01-08  6:04 ` David Miller
2007-12-20 15:54 John W. Linville
2007-12-16  4:31 John W. Linville
2007-12-17 19:34 ` John W. Linville
2007-12-17 20:07   ` David Miller
2007-12-17 20:18   ` Jeff Garzik
2007-12-17 21:10 ` Jeff Garzik
2007-11-30  3:29 John W. Linville
2007-12-01 21:20 ` Jeff Garzik
2007-11-06 20:07 John W. Linville
2007-11-07 19:13 ` John W. Linville
2007-11-07 19:24   ` Jeff Garzik
2007-10-18 22:09 John W. Linville
2007-10-20  3:04 ` Jeff Garzik
2007-10-03  1:20 John W. Linville
2007-10-03 17:39 ` Jeff Garzik
2007-08-06 20:14 John W. Linville
2007-08-07 21:25 ` Jeff Garzik

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=4725AC5E.3080006@garzik.org \
    --to=jeff@garzik.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --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 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.