From: "John W. Linville" <linville@tuxdriver.com>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: Felix Fietkau <nbd@openwrt.org>,
linux-wireless@vger.kernel.org, Greg KH <greg@kroah.com>
Subject: Re: [PATCH] ath9k_hw: fix endian issues with CTLs on AR9003
Date: Mon, 29 Nov 2010 16:27:08 -0500 [thread overview]
Message-ID: <20101129212707.GG8199@tuxdriver.com> (raw)
In-Reply-To: <AANLkTimS1hsfoOe9bdgad7kkUPPcMVjd_kB_Ru8kbqt8@mail.gmail.com>
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
> <linville@tuxdriver.com> 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"?
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2010-11-29 21:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-20 18:50 [PATCH] ath9k_hw: fix endian issues with CTLs on AR9003 Felix Fietkau
2010-11-22 20:15 ` John W. Linville
2010-11-22 20:52 ` Felix Fietkau
2010-11-29 19:50 ` John W. Linville
2010-11-29 21:19 ` Luis R. Rodriguez
2010-11-29 21:27 ` John W. Linville [this message]
2010-11-29 21:35 ` Luis R. Rodriguez
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=20101129212707.GG8199@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=greg@kroah.com \
--cc=linux-wireless@vger.kernel.org \
--cc=lrodriguez@atheros.com \
--cc=nbd@openwrt.org \
/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;
as well as URLs for NNTP newsgroup(s).