From: Stanislaw Gruszka <stf_xl@wp.pl>
To: Kevin Lo <kevlo@kevlo.org>
Cc: John Linville <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, users@rt2x00.serialmonkey.com
Subject: Re: [rt2x00-users] [PATCH v2] rt2x00: rt2800lib: no need to toggle RF R30 bit 7 twice
Date: Tue, 8 Oct 2013 12:46:20 +0200 [thread overview]
Message-ID: <20131008104620.GA15764@localhost.localdomain> (raw)
In-Reply-To: <525269F0.5000802@kevlo.org>
On Mon, Oct 07, 2013 at 03:59:44PM +0800, Kevin Lo wrote:
> rt2800_rfcsr_read(rt2x00dev, 23, &rfcsr);
> rt2x00_set_field8(&rfcsr, RFCSR23_FREQ_OFFSET,
> rt2x00dev->freq_offset);
> rt2800_rfcsr_write(rt2x00dev, 23, rfcsr);
NACK, still malformed
next prev parent reply other threads:[~2013-10-08 10:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-07 7:59 [PATCH v2] rt2x00: rt2800lib: no need to toggle RF R30 bit 7 twice Kevin Lo
2013-10-08 10:46 ` Stanislaw Gruszka [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-10-07 8:02 Kevin Lo
2013-10-08 10:47 ` [rt2x00-users] " Stanislaw Gruszka
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=20131008104620.GA15764@localhost.localdomain \
--to=stf_xl@wp.pl \
--cc=kevlo@kevlo.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).