All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Ike Panhc <ike.pan@canonical.com>
Cc: reinette chatre <reinette.chatre@intel.com>,
	"Zhu, Yi" <yi.zhu@intel.com>,
	"John W. Linville" <linville@tuxdriver.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Guy, Wey-Yi W" <wey-yi.w.guy@intel.com>,
	"Winkler, Tomas" <tomas.winkler@intel.com>,
	"stable@kernel.org" <stable@kernel.org>
Subject: Re: [stable] [PATCH 2/2] iwlwifi: unify iwl_setup_rxon_timing
Date: Wed, 16 Dec 2009 19:29:25 -0800	[thread overview]
Message-ID: <20091217032925.GA21374@kroah.com> (raw)
In-Reply-To: <4B298ECF.7050009@canonical.com>

On Thu, Dec 17, 2009 at 09:52:15AM +0800, Ike Panhc wrote:
> reinette chatre wrote:
> > On Tue, 2009-12-15 at 22:46 -0800, Ike Panhc wrote:
> > 
> >> But Please consider applying the first patch (change IWL6000_UCODE_API_MAX
> >> to v4) to 2.6.31-stable tree. It will be good to use v4 firmware on iwl6000.
> > 
> > Please no. This will effectively enable 6000 series in 2.6.31. We did
> > not target 2.6.31 for 6000 series enabling and more patches, which are
> > in 2.6.32, are required for 6000 series to work well.
> > 
> > Reinette
> > 
> Got it, so backport any patch for iwl6000 to 2.6.31-stable is not reasonable.

Bugfixes are fine, but that is not what this is.

Please go read the file, Documentation/stable_kernel_rules.txt to give
you an idea of what we are expecting here.

thanks,

greg k-h

  reply	other threads:[~2009-12-17  3:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-15  3:44 [PATCH 0/2] Fix iwl6000 does not work in 2.6.31 kernel Ike Panhc
2009-12-15  3:44 ` [PATCH 1/2] iwlwifi: change IWL6000_UCODE_API_MAX to v4 Ike Panhc
2009-12-15  3:45 ` [PATCH 2/2] iwlwifi: unify iwl_setup_rxon_timing Ike Panhc
2009-12-15  4:15   ` [stable] " Greg KH
2009-12-15  7:02     ` Ike Panhc
2009-12-15 13:49       ` Greg KH
2009-12-15 16:31         ` John W. Linville
2009-12-15 19:42           ` reinette chatre
2009-12-15 19:49             ` Greg KH
2009-12-16  6:46               ` Ike Panhc
2009-12-16 14:55                 ` Greg KH
2009-12-16 17:05                 ` reinette chatre
2009-12-17  1:52                   ` Ike Panhc
2009-12-17  3:29                     ` Greg KH [this message]
2009-12-15 16:34         ` Marcel Holtmann
2009-12-15 16:39           ` John W. Linville
2009-12-15 17:14             ` Greg KH
2009-12-15 17:27               ` Stefan Bader

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=20091217032925.GA21374@kroah.com \
    --to=greg@kroah.com \
    --cc=ike.pan@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=reinette.chatre@intel.com \
    --cc=stable@kernel.org \
    --cc=tomas.winkler@intel.com \
    --cc=wey-yi.w.guy@intel.com \
    --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 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.