From: Kevin Lo <kevlo@kevlo.org>
To: Gabor Juhos <juhosg@openwrt.org>
Cc: John Linville <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, users@rt2x00.serialmonkey.com
Subject: Re: [PATCH] rt2x00: rt2800lib: remove duplicate rf_vals for RF3053.
Date: Fri, 04 Oct 2013 09:41:12 +0800 [thread overview]
Message-ID: <524E1CB8.3040004@kevlo.org> (raw)
In-Reply-To: <524D5DCE.80601@openwrt.org>
Gabor Juhos wrote:
> 2013.10.03. 9:48 keltezéssel, Kevin Lo írta:
>> We already have rf_vals_3x with same values. Hence rf_vals_3053 is removed
>> in this patch.
>>
>> Signed-off-by: Kevin Lo <kevlo@kevlo.org>
> For completeness, the comment of rf_vals_3x should be updated to indicate that
> it also supports RF3053. Otherwise the patch is fine.
Ok, I'll send an updated patch, thanks.
>
> -Gabor
>
Kevin
prev parent reply other threads:[~2013-10-04 1:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-03 7:48 [PATCH] rt2x00: rt2800lib: remove duplicate rf_vals for RF3053 Kevin Lo
2013-10-03 8:42 ` [rt2x00-users] " Paul Menzel
2013-10-03 12:06 ` Gabor Juhos
2013-10-04 1:41 ` Kevin Lo [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=524E1CB8.3040004@kevlo.org \
--to=kevlo@kevlo.org \
--cc=juhosg@openwrt.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=users@rt2x00.serialmonkey.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).