public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Ike Panhc <ike.pan@canonical.com>
Cc: linux-kernel@vger.kernel.org,
	Tomas Winkler <tomas.winkler@intel.com>,
	stable@kernel.org, Wey-Yi Guy <wey-yi.w.guy@intel.com>
Subject: Re: [stable] [PATCH 2/2] iwlwifi: unify iwl_setup_rxon_timing
Date: Tue, 15 Dec 2009 05:49:43 -0800	[thread overview]
Message-ID: <20091215134943.GA11667@kroah.com> (raw)
In-Reply-To: <4B273479.6050502@canonical.com>

On Tue, Dec 15, 2009 at 03:02:17PM +0800, Ike Panhc wrote:
> Greg KH wrote:
> > On Tue, Dec 15, 2009 at 11:45:10AM +0800, Ike Panhc wrote:
> >> This patch unifies setup_rxon_timing funcions
> >> of AGN and 3945. HWs differ only in supported maximal
> >> beacon interval. This is reflected in hw_paras.max_beacon_itrvl
> >>
> >> Signed-off-by: Tomas Winkler <tomas.winkler@intel.com>
> >> Signed-off-by: Reinette Chatre <reinette.chatre@intel.com>
> >> Signed-off-by: John W. Linville <linville@tuxdriver.com>
> >> (cherry picked from commit 2c2f3b33888419fb9e7d015b9dc67b9db4437efa)
> >>
> >> Conflicts:
> >>
> >> 	drivers/net/wireless/iwlwifi/iwl-dev.h
> > 
> > What does this mean?
> > 
> After cherry-pick:
> 
> --- a/drivers/net/wireless/iwlwifi/iwl-dev.h
> +++ b/drivers/net/wireless/iwlwifi/iwl-dev.h
> @@@ -625,7 -608,7 +625,11 @@@ struct iwl_hw_params 
> 	u8  max_stations;
> 	u8  bcast_sta_id;
> 	u8 fat_channel;
> ++<<<<<<< HEAD:drivers/net/wireless/iwlwifi/iwl-dev.h
>  +	u8 sw_crypto;
> ++=======
> +	u8  max_beacon_itrvl;   /* in 1024 ms */
> ++>>>>>>> 2c2f3b3... iwlwifi: unify iwl_setup_rxon_timing:drivers/net/wireless/iwlwifi/iwl-dev.h
> 	u32 max_inst_size;
> 	u32 max_data_size;
> 	u32 max_bsm_size;
> 
> The sw_crypto is removed in the prior commit (90e8e4), and the commit
> is not in the stable tree. We still need sw_crypto.
> 
> So, the patch is modified to keep sw_crypto.

And why would we care?  We've never used this kind of marking before in
the kernel changelogs that I know of.

> >> CC: stable@kernel.org
> >> Signed-off-by: Ike Panhc <ike.pan@canonical.com>
> >>
> >> BugLink: http://bugs.launchpad.net/bugs/496496
> > 
> > What are you expecting this patch to be applied to?
> > 
> > confused,
> Please consider applying to linux-2.6.31.y

I need the subsystem maintainer to agree with this, have they?

thanks,

greg k-h

  reply	other threads:[~2009-12-15 13:54 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 [this message]
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
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=20091215134943.GA11667@kroah.com \
    --to=greg@kroah.com \
    --cc=ike.pan@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@kernel.org \
    --cc=tomas.winkler@intel.com \
    --cc=wey-yi.w.guy@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