linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Reinette Chatre <reinette.chatre@intel.com>
To: linville@tuxdriver.com
Cc: linux-wireless@vger.kernel.org,
	ipw3945-devel@lists.sourceforge.net,
	Reinette Chatre <reinette.chatre@intel.com>
Subject: [PATCH 0/14] iwlwifi driver updates 07/17/2009
Date: Fri, 17 Jul 2009 09:30:13 -0700	[thread overview]
Message-ID: <1247848227-24031-1-git-send-email-reinette.chatre@intel.com> (raw)

This series contains something of everything. We include some general fixes
(new hardware stability, log output corrections, correct data used to compute led
 blinking rate, better error detection, including better handling of
 failures during ucode loading) and general cleanup. Some new
features include the addition of code to deal with a new ucode header
format that includes a build number. This new ucode header format is
currently only used for new hardware for which the ucode is not public yet.
We also include a new debugfs file to show led status and include a revamp
of the debug interface.

We include a bugfix for http://bugzilla.kernel.org/show_bug.cgi?id=13742
which targets wireless-testing and 2.6.31.

[PATCH 01/14] iwlagn: modify digital SVR for 1000
[PATCH 02/14] iwlwifi: fix rx signal quality reporting in dmesg
[PATCH 03/14] iwlwifi: Handle new firmware file with ucode build number in header
[PATCH 04/14] iwlwifi: make led functions generic
[PATCH 05/14 w-t and 2.6.31] iwlagn: do not send key clear commands when rfkill enabled
[PATCH 06/14] iwlwifi: add led debugfs function
[PATCH 07/14] iwlwifi: Led blinking counting both tx and rx
[PATCH 08/14] iwlwifi: checking unknown HW type
[PATCH 09/14] iwlwifi: update 1000 series API version to match firmware
[PATCH 10/14] iwlwifi: uCode Alive notification with timeout
[PATCH 11/14] iwlwifi: make debug level more user friendly
[PATCH 12/14] iwlwifi: clarify hardware error message
[PATCH 13/14] iwlwifi: inform user about rfkill state changes
[PATCH 14/14] iwlwifi: change iwl_enable/disable_interrupts to "inline"


Reinette


             reply	other threads:[~2009-07-17 16:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-17 16:30 Reinette Chatre [this message]
2009-07-17 16:30 ` [PATCH 01/14] iwlagn: modify digital SVR for 1000 Reinette Chatre
2009-07-17 16:30   ` [PATCH 02/14] iwlwifi: fix rx signal quality reporting in dmesg Reinette Chatre
2009-07-17 16:30     ` [PATCH 03/14] iwlwifi: Handle new firmware file with ucode build number in header Reinette Chatre
2009-07-17 16:30       ` [PATCH 04/14] iwlwifi: make led functions generic Reinette Chatre
2009-07-17 16:30         ` [PATCH 05/14 w-t and 2.6.31] iwlagn: do not send key clear commands when rfkill enabled Reinette Chatre
2009-07-17 16:30           ` [PATCH 06/14] iwlwifi: add led debugfs function Reinette Chatre
2009-07-17 16:30             ` [PATCH 07/14] iwlwifi: Led blinking counting both tx and rx Reinette Chatre
2009-07-17 16:30               ` [PATCH 08/14] iwlwifi: checking unknown HW type Reinette Chatre
2009-07-17 16:30                 ` [PATCH 09/14] iwlwifi: update 1000 series API version to match firmware Reinette Chatre
2009-07-17 16:30                   ` [PATCH 10/14] iwlwifi: uCode Alive notification with timeout Reinette Chatre
2009-07-17 16:30                     ` [PATCH 11/14] iwlwifi: make debug level more user friendly Reinette Chatre
2009-07-17 16:30                       ` [PATCH 12/14] iwlwifi: clarify hardware error message Reinette Chatre
2009-07-17 16:30                         ` [PATCH 13/14] iwlwifi: inform user about rfkill state changes Reinette Chatre
2009-07-17 16:30                           ` [PATCH 14/14] iwlwifi: change iwl_enable/disable_interrupts to "inline" Reinette Chatre
2009-07-30 20:12           ` [PATCH 05/14 w-t and 2.6.31] iwlagn: do not send key clear commands when rfkill enabled reinette chatre

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=1247848227-24031-1-git-send-email-reinette.chatre@intel.com \
    --to=reinette.chatre@intel.com \
    --cc=ipw3945-devel@lists.sourceforge.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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).