From: Bruno Randolf <br1@einfach.org>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: ath5k-devel@lists.ath5k.org, linux-wireless@vger.kernel.org,
linville@tuxdriver.com
Subject: Re: [ath5k-devel] [PATCH v2] ath5k: fix I/Q calibration (for real)
Date: Tue, 9 Mar 2010 09:34:59 +0900 [thread overview]
Message-ID: <201003090934.59740.br1@einfach.org> (raw)
In-Reply-To: <43e72e891003080824l74ecd4fbrf5a02e51c275c9b1@mail.gmail.com>
On Tuesday 09 March 2010 01:24:48 Luis R. Rodriguez wrote:
> >> Thanks Bruno, are these stable fixes?
> >
> > hi luis!
> >
> > i think so. the behaviour before was completely broken, now it's better.
> >
> > but i'm not sure about that whole Cc: stable@kernel.org thing... (sorry
> > i've been away for a while)... i read
> > Documentation/stable_kernel_rules.txt but still not sure if that applies
> > for this patch.
>
> Just add:
>
> Cc: stable@kernel.org
>
> below your Singed-off-by on the commit log entry. That list will get
> spammed once the patch is merged on Linus' tree.
i understand that.
the question is more if my patch justifies bothering 'stable' or not.
as i said, in my point of view ath5k has several problems right now
(performace and stability), and i guess nobody will be using it seriously in
actual production use (does anyone?). so i think it does not really matter if
this or any of my other patches go into stable sooner or later. does it?
bruno
next prev parent reply other threads:[~2010-03-09 0:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 2:59 [PATCH v2] ath5k: fix I/Q calibration (for real) Bruno Randolf
2010-03-08 3:56 ` Luis R. Rodriguez
2010-03-08 4:17 ` [ath5k-devel] " Bruno Randolf
2010-03-08 16:24 ` Luis R. Rodriguez
2010-03-09 0:34 ` Bruno Randolf [this message]
2010-03-09 0:47 ` Luis R. Rodriguez
2010-03-09 0:50 ` Bruno Randolf
2010-03-09 1:21 ` Luis R. Rodriguez
2010-03-09 3:10 ` Bob Copeland
2010-03-09 3:32 ` Luis R. Rodriguez
2010-03-09 5:56 ` Bruno Randolf
2010-03-09 6:45 ` Bob Copeland
2010-03-08 12:45 ` Jorge Boncompte [DTI2]
2010-03-09 0:24 ` Bruno Randolf
2010-03-09 0:33 ` Jorge Boncompte [DTI2]
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=201003090934.59740.br1@einfach.org \
--to=br1@einfach.org \
--cc=ath5k-devel@lists.ath5k.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.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.