From: Kalle Valo <kvalo@codeaurora.org>
To: Kevin Lo <kevlo@kevlo.org>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
Ping-Ke Shih <pkshih@realtek.com>,
Yan-Hsuan Chuang <yhchuang@realtek.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] rtlwifi: fix REG_USTIME_TSF register definition
Date: Sun, 11 Jun 2017 11:18:38 +0300 [thread overview]
Message-ID: <87y3szos2p.fsf@purkki.adurom.net> (raw)
In-Reply-To: <20170610142316.GA9284@ns.kevlo.org> (Kevin Lo's message of "Sat, 10 Jun 2017 22:23:16 +0800")
Kevin Lo <kevlo@kevlo.org> writes:
> Sorry for the top post. This patch has an Acked-by Yan-Hsuan Chuang.
>
> On Wed, Jun 07, 2017 at 09:43:21AM +0800, =E8=8E=8A=E5=BD=A5=E5=AE=A3 wro=
te:
>> Yes, the register 0x55c is for REG_USTIME_TSF.
>> And 0x551 is for BCN_CTRL1.
>>=20
>>=20
>> Acked-by: Yan-Hsuan, Chuang <yhchuang@realtek.com>
>>=20
>> 2017-05-19 23:02 GMT+08:00 Kevin Lo <kevlo@kevlo.org>:
>>=20
>> > The REG_USTIME_TSF (US Time Tuning for TSF) definition of Realtek chips
>> > should be 0x55C.
>> >
>> > Signed-off-by: Kevin Lo <kevlo@kevlo.org>
I don't see Yan-Hsuan's ack on the mailing list (maybe it was dropped
because of HTML?) and hence neither in patchwork:
https://patchwork.kernel.org/patch/9737421/
Yan-Hsuan or Larry, can you please resend the ack so that patchwork sees
it?
--=20
Kalle Valo
next prev parent reply other threads:[~2017-06-11 8:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-19 15:02 [PATCH] rtlwifi: fix REG_USTIME_TSF register definition Kevin Lo
2017-05-24 8:46 ` Kalle Valo
[not found] ` <CA+R5OdtxiN4XBZg3k-Suamj5r4+=jDY-10HdUCHuqb=Nt-baqg@mail.gmail.com>
2017-06-10 14:23 ` [PATCH] " Kevin Lo
2017-06-11 8:18 ` Kalle Valo [this message]
2017-06-11 13:24 ` Kevin Lo
2017-06-21 15:24 ` Kalle Valo
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=87y3szos2p.fsf@purkki.adurom.net \
--to=kvalo@codeaurora.org \
--cc=Larry.Finger@lwfinger.net \
--cc=kevlo@kevlo.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@realtek.com \
--cc=yhchuang@realtek.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).