Return-path: Received: from mail-iw0-f174.google.com ([209.85.214.174]:37604 "EHLO mail-iw0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751258Ab0K2Vfl (ORCPT ); Mon, 29 Nov 2010 16:35:41 -0500 Received: by iwn5 with SMTP id 5so609273iwn.19 for ; Mon, 29 Nov 2010 13:35:41 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <20101129212707.GG8199@tuxdriver.com> References: <1290279018-29716-1-git-send-email-nbd@openwrt.org> <20101122201511.GG2117@tuxdriver.com> <4CEAD7FA.1060107@openwrt.org> <20101129195038.GD8199@tuxdriver.com> <20101129212707.GG8199@tuxdriver.com> From: "Luis R. Rodriguez" Date: Mon, 29 Nov 2010 13:35:20 -0800 Message-ID: Subject: Re: [PATCH] ath9k_hw: fix endian issues with CTLs on AR9003 To: "John W. Linville" Cc: Felix Fietkau , linux-wireless@vger.kernel.org, Greg KH Content-Type: text/plain; charset=UTF-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Mon, Nov 29, 2010 at 1:27 PM, John W. Linville wrote: > On Mon, Nov 29, 2010 at 01:19:19PM -0800, Luis R. Rodriguez wrote: >> On Mon, Nov 29, 2010 at 11:50 AM, John W. Linville >> wrote: > >> > After being chided for having an excessive number of patches in -next >> > with "Cc: stable@kernel.org", I would prefer to avoid (or strongly >> > limit) merging such patches that way. >> >> Is this a bad thing? > > The point was that if it was a fix worth of consideration for stable > then it generally ought to be worth of consideration for the current > release. > >> Come to think of it we didn't get OTP patches in for 2.6.36 so I am >> not considering we should just disable AR9003 from the PCI ID list for >> ath9k as all cards sold should have it so in that case this patch >> would just need to go to 2.6.37 and not 2.6.36. > > Do you perhaps mean "need to go to 2.6.38 and not 2.6.37"? Yeah sorry, proper OTP likely didn't make it for 2.6.37, not sure now. Will have to check and get back to you. Luis