public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: reinette.chatre@intel.com
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
	ipw3945-devel@lists.sourceforge.net
Subject: Re: [PATCH 0/7] iwlwifi updates 12/10/2009
Date: Thu, 10 Dec 2009 14:59:35 -0800 (PST)	[thread overview]
Message-ID: <20091210.145935.135534027.davem@davemloft.net> (raw)
In-Reply-To: <1260485392.25564.6308.camel@rc-desk>

From: reinette chatre <reinette.chatre@intel.com>
Date: Thu, 10 Dec 2009 14:49:52 -0800

> Sorry that I introduced confusion now ... perhaps I should submit fixes
> and features in separate series to prevent this in the future.

That sounds like a good idea to me.

  reply	other threads:[~2009-12-10 22:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-10 22:37 [PATCH 0/7] iwlwifi updates 12/10/2009 Reinette Chatre
2009-12-10 22:37 ` [PATCH 1/7 w-t and 2.6.33] iwlwifi: allocated rx page accounting cleanup Reinette Chatre
2009-12-10 22:37 ` [PATCH 2/7 w-t and 2.6.33] iwlwifi: power up all devices for EEPROM read Reinette Chatre
2009-12-10 22:37 ` [PATCH 3/7 w-t and 2.6.33] iwlwifi: fix syslog message for event log dump size Reinette Chatre
2009-12-10 22:37 ` [PATCH 4/7] iwlwifi: log CT_CARD_DISABLED flag Reinette Chatre
2009-12-10 22:37 ` [PATCH 5/7] iwlwifi: dump "Control and Status Register" when detect uCode HW/SW error Reinette Chatre
2009-12-10 22:37 ` [PATCH 6/7] iwlwifi: add continuous uCode event log capability Reinette Chatre
2009-12-10 22:37 ` [PATCH 7/7] iwlwifi: use new mac80211 SMPS Reinette Chatre
2009-12-10 22:42 ` [PATCH 0/7] iwlwifi updates 12/10/2009 David Miller
2009-12-10 22:49   ` reinette chatre
2009-12-10 22:59     ` David Miller [this message]
2009-12-10 23:14       ` 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=20091210.145935.135534027.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=ipw3945-devel@lists.sourceforge.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=reinette.chatre@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