linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Zhu Yi <yi.zhu@intel.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 00/10] iwlwifi driver 08/04 updates
Date: Tue, 5 Aug 2008 09:03:20 -0400	[thread overview]
Message-ID: <20080805130320.GA4276@tuxdriver.com> (raw)
In-Reply-To: <1217918197.3107.64.camel@debian.sh.intel.com>

On Tue, Aug 05, 2008 at 02:36:37PM +0800, Zhu Yi wrote:
> On Mon, 2008-08-04 at 16:00 +0800, Zhu Yi wrote:
> > Hi John,
> > 
> > Here is another series of iwlwifi driver update. Note, the patch 10/10 fixes
> > a merge problem for wireless-testing GIT with upstream.
> > 
> > Thanks,
> > -yi
> > 
> > [PATCH 01/10] iwlwifi: HW bug fixes
> > [PATCH 02/10] iwlwifi: memory allocation optimization
> > [PATCH 03/10] iwlwifi: kill struct iwl4965_lq_mngr
> > [PATCH 04/10] iwlwifi: implement iwl5000_calc_rssi
> > [PATCH 05/10] iwlwifi: fix unhandled interrupt when HW rfkill is on
> > [PATCH 06/10] iwlwifi: cleanup iwl_tx_skb
> > [PATCH 07/10] iwlwifi: add level for debugging host command
> > [PATCH 08/10] iwlwifi: decrement rx skb counter in scan abort handler
> > [PATCH 09/10] iwlwifi: grap nic access before accessing periphery registers
> > [PATCH 10/10] iwl3945: fix merge mistake for packet injection
> 
> Hi John,
> 
> I see you merged only partial of this series. What's happen to the
> patches 03, 06 and 07?

I don't see those as fixes, only cleanups.  The merge window is closed
for 2.6.27.  If those are in fact fixes then please explain.

Thanks,

John
-- 
John W. Linville
linville@tuxdriver.com

  reply	other threads:[~2008-08-05 13:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-04  8:00 [PATCH 00/10] iwlwifi driver 08/04 updates Zhu Yi
2008-08-04  8:00 ` [PATCH 01/10] iwlwifi: HW bug fixes Zhu Yi
2008-08-04  8:00   ` [PATCH 02/10] iwlwifi: memory allocation optimization Zhu Yi
2008-08-04  8:00     ` [PATCH 03/10] iwlwifi: kill struct iwl4965_lq_mngr Zhu Yi
2008-08-04  8:00       ` [PATCH 04/10] iwlwifi: implement iwl5000_calc_rssi Zhu Yi
2008-08-04  8:00         ` [PATCH 05/10] iwlwifi: fix unhandled interrupt when HW rfkill is on Zhu Yi
2008-08-04  8:00           ` [PATCH 06/10] iwlwifi: cleanup iwl_tx_skb Zhu Yi
2008-08-04  8:00             ` [PATCH 07/10] iwlwifi: add level for debugging host command Zhu Yi
2008-08-04  8:00               ` [PATCH 08/10] iwlwifi: decrement rx skb counter in scan abort handler Zhu Yi
2008-08-04  8:00                 ` [PATCH 09/10] iwlwifi: grap nic access before accessing periphery registers Zhu Yi
2008-08-04  8:00                   ` [PATCH 10/10] iwl3945: fix merge mistake for packet injection Zhu Yi
2008-08-04 14:48                 ` [PATCH 08/10] iwlwifi: decrement rx skb counter in scan abort handler Ian Schram
2008-08-05  6:36 ` [PATCH 00/10] iwlwifi driver 08/04 updates Zhu Yi
2008-08-05 13:03   ` John W. Linville [this message]
2008-08-05 15:36     ` Tomas Winkler
2008-08-06  1:04     ` Zhu Yi
2008-08-06 13:06       ` 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=20080805130320.GA4276@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=yi.zhu@intel.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 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).