From: "John W. Linville" <linville@tuxdriver.com>
To: Andrea Merello <andrea.merello@gmail.com>
Cc: linux-wireless@vger.kernel.org, Alessandro Di Marco <dmr@c0nc3pt.com>
Subject: Re: [PATCH] Rtl8180 max2820 ch14
Date: Wed, 14 May 2008 16:09:27 -0400 [thread overview]
Message-ID: <20080514200927.GC15712@tuxdriver.com> (raw)
In-Reply-To: <c68f135e0805100432n5d90e9d1p26d2bd35ac99f994@mail.gmail.com>
On Sat, May 10, 2008 at 01:32:34PM +0200, Andrea Merello wrote:
> Rtl8180: fix wrong parameter in RF code function invokation for maxim radio
>
> The max2820 RF code needs to invoke max2820_write_phy_antenna every time the
> channel is being switch.
>
> This should be done passing the channel number to that function.
> Incorrectly we were passing the same value that is written on the
> channel RF register.
> This may cause problems when operating on ch 14.
>
> This patch fixes it.
>
> Thanks to Alessandro Di Marco who found this issue!
>
>
> signed-off-by: Andrea Merello <andreamrl@tiscali.it>
> ---
>
> --- a/drivers/net/wireless/rtl8180_max2820.c 2008-02-02
> 14:48:52.000000000 +0100
> +++ b/drivers/net/wireless/rtl8180_max2820.c 2008-02-02
> 14:55:29.000000000 +0100
> @@ -86,7 +86,7 @@ static void max2820_rf_set_channel(struc
> * sa2400, for MAXIM we do this directly from BB */
> rtl8180_write_phy(dev, 3, txpw);
>
> - max2820_write_phy_antenna(dev, chan);
> + max2820_write_phy_antenna(dev, chan_idx + 1);
> write_max2820(dev, 3, chan);
> }
This one didn't trigger any warnings, but it was whitespace damaged.
I'll hold-off on applying this one since I presume you will be
resubmitting the other patches. I'll apply them all at once then.
John
--
John W. Linville
linville@tuxdriver.com
prev parent reply other threads:[~2008-05-14 20:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-10 11:32 PATCH Rtl8180 ch14 [2/3] Andrea Merello
2008-05-14 20:09 ` John W. Linville [this message]
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=20080514200927.GC15712@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=andrea.merello@gmail.com \
--cc=dmr@c0nc3pt.com \
--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).