From: reinette chatre <reinette.chatre@intel.com>
To: David Miller <davem@davemloft.net>
Cc: "linville@tuxdriver.com" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ipw3945-devel@lists.sourceforge.net"
<ipw3945-devel@lists.sourceforge.net>
Subject: Re: [PATCH 0/7] iwlwifi updates 12/10/2009
Date: Thu, 10 Dec 2009 14:49:52 -0800 [thread overview]
Message-ID: <1260485392.25564.6308.camel@rc-desk> (raw)
In-Reply-To: <20091210.144239.110141276.davem@davemloft.net>
On Thu, 2009-12-10 at 14:42 -0800, David Miller wrote:
> From: Reinette Chatre <reinette.chatre@intel.com>
> Date: Thu, 10 Dec 2009 14:37:20 -0800
>
> > In this series we also include support for the new mac80211 spatial
> > multiplexing support.
>
> No more new features for 2.6.33, sorry.
>
> Only bug fixes at this time.
Absolutely - the feature you quoted was not intended for 2.6.33 ...
especially since the mac80211 API it relies on is not there either.
The series I posted included both fixes for 2.6.33 and features for
2.6.34. The one you quoted is a feature for 2.6.34.
I tried to be clear in the fixes we target for 2.6.33 by clearly
mentioning them in the commit message like so:
On Thu, 2009-12-10 at 14:37 -0800, Chatre, Reinette wrote:
> This series includes three fixes targeting 2.6.33:
> - "iwlwifi: power up all devices for EEPROM read" fixes a issue where
> devices are unable to be initialized on certain platforms due to too
> aggressive power savings.
> - "iwlwifi: allocated rx page accounting cleanup" fixes some accounting
> issues in the recent paged RX work
> - "iwlwifi: fix syslog message for event log dump size" fixes the problem
> where the entire debug log was not printed when requested by user
>
... and also annotating the Subject line of the fixes like so:
[PATCH X/XX w-t and 2.6.33] iwl.....
With the above I hoped to make it clear that the patch is targeting both
wireless-testing (for 2.6.34) and 2.6.33 as a fix. Patches targeting
2.6.34 do not have special "tags" after "PATCH".
This is the way we have been submitting patches for a long time now.
Sorry that I introduced confusion now ... perhaps I should submit fixes
and features in separate series to prevent this in the future.
Reinette
next prev parent reply other threads:[~2009-12-10 22:49 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 [this message]
2009-12-10 22:59 ` David Miller
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=1260485392.25564.6308.camel@rc-desk \
--to=reinette.chatre@intel.com \
--cc=davem@davemloft.net \
--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