From: Bruno Randolf <br1@einfach.org>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Bob Copeland <me@bobcopeland.com>,
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 14:56:37 +0900 [thread overview]
Message-ID: <201003091456.37577.br1@einfach.org> (raw)
In-Reply-To: <43e72e891003081932h49340b6aia3fb6fd1e60ae8d7@mail.gmail.com>
On Tuesday 09 March 2010 12:32:33 Luis R. Rodriguez wrote:
> On Mon, Mar 8, 2010 at 7:10 PM, Bob Copeland <me@bobcopeland.com> wrote:
> > On Mon, Mar 8, 2010 at 8:21 PM, Luis R. Rodriguez <mcgrof@gmail.com>
wrote:
> >> On Mon, Mar 8, 2010 at 4:50 PM, Bruno Randolf <br1@einfach.org> wrote:
> >>>> > 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?).
> >
> > Yes, people do use ath5k in production. Some large companies.
> >
> >>>> 2.6.32 will be used by a lot of "enterprise" releases, I'd prefer
> >>>> connection stability fixes do indeed go in for 2.6.32 for ath5k
> >>>
> >>> sure, as i said, i don't mind. :)
> >>
> >> Alright lets skip stable for this.
> >
> > Wow this whole line of conversation is confusing :)
>
> Hehe. sorry well I was talking to Bruno about the "stable"
> qualifications of this fix, and it doesn't fix an oops or serious bug,
> but it certainly can improve performance but I haven't myself seen
> numbers and would hate to justify just about pushing anything
> upstream.
>
> > If this fixes a calibration bug it needs to go to stable.
>
> Perhaps a little more elaboration on the commit log on the impact and
> how this helps and how much would help.
ok. to stop the confusion, i'll add cc: stable.
bruno
next prev parent reply other threads:[~2010-03-09 5:56 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
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 [this message]
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=201003091456.37577.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 \
--cc=me@bobcopeland.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;
as well as URLs for NNTP newsgroup(s).