From: "John W. Linville" <linville@tuxdriver.com>
To: Anna Neal <anna@cozybit.com>
Cc: Dan Williams <dcbw@redhat.com>,
linux-wireless@vger.kernel.org, libertas-dev@lists.infradead.org
Subject: Re: [PATCH] libertas: Improvements on automatic tx power control via SIOCSIWTXPOW.
Date: Thu, 11 Sep 2008 13:24:07 -0400 [thread overview]
Message-ID: <20080911172406.GG3423@tuxdriver.com> (raw)
In-Reply-To: <aa050c750809111013r4c941ed4l250c5ae5e019c720@mail.gmail.com>
On Thu, Sep 11, 2008 at 10:13:20AM -0700, Anna Neal wrote:
> On Thu, Sep 11, 2008 at 10:03 AM, Anna Neal <anna@cozybit.com> wrote:
> > On Thu, Sep 11, 2008 at 8:34 AM, Dan Williams <dcbw@redhat.com> wrote:
> >> On Wed, 2008-09-10 at 16:45 -0700, Anna Neal wrote:
> >>> Improved the tx power control configuration per Dan Williams suggestions. Added
> >>> a firmware version check because the current implementation will only work for
> >>> below version 9.
> >>>
> >>> Signed-off-by: Anna Neal <anna@cozybit.com>
> >>
> >> One more round, sorry! :)
> >>
> >> First, until the patch has actually been applied, could you post
> >> complete diffs? This is a patch against the previous patch, but it's
> >> best to keep the whole patch together until it's committed by John to
> >> the master wireless tree.
> >>
> >> Second, since you get to respin the patch anyway for this, the TPC
> >> Config stuff should be just fine on V9+ firmware, only the
> >> POWER_ADAPT_CFG command is incompatible on V9+. I probably wasn't clear
> >> enough about this yesterday. Any chance you could move the TPC config
> >> commands out of the firmware check and just the PACFG ones < V9?
> >>
> >> Thanks!
> >> Dan
> >
> > No problem, will send a new patch later today.
> >
> > I just wanted to point out that it seems the original patch was
> > already committed by John.
> >
> > Here is the link:
> > http://git.kernel.org/?p=linux/kernel/git/linville/wireless-testing.git;a=commith=cdd799f13e3a2a47b501286551ba9386e8936272
> >
> > Thanks,
> > Anna
>
> I'm sorry, I sent a bad link.
>
> Here is a good one.
>
> http://git.kernel.org/?p=linux/kernel/git/linville/wireless-testing.git;a=commit&h=cdd799f13e3a2a47b501286551ba9386e8936272
FWIW, it hasn't been sent to Dave M. yet -- it's only in
wireless-testing.
That said, I'm fine with either a whole new patch or the incremental
one. But if Dan wants a new one and you don't mind...
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2008-09-11 17:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-10 23:45 [PATCH] libertas: Improvements on automatic tx power control via SIOCSIWTXPOW Anna Neal
2008-09-11 15:34 ` Dan Williams
2008-09-11 17:03 ` Anna Neal
2008-09-11 17:13 ` Anna Neal
2008-09-11 17:24 ` John W. Linville [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-09-11 18:17 Anna Neal
2008-09-11 18:37 ` Johannes Berg
2008-09-11 18:56 ` Anna Neal
2008-09-11 19:12 ` Johannes Berg
2008-09-15 5:44 ` Dan Williams
2008-09-17 18:23 ` Anna Neal
2008-09-25 23:19 Anna Neal
2008-09-26 14:49 ` Dan Williams
2008-09-26 16:26 ` John W. Linville
2008-09-29 20:59 ` Dan Williams
2008-09-29 21:20 ` John W. Linville
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=20080911172406.GG3423@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=anna@cozybit.com \
--cc=dcbw@redhat.com \
--cc=libertas-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.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).