From: Kevin Lo <kevlo@kevlo.org>
To: Kalle Valo <kvalo@codeaurora.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 21:24:24 +0800 [thread overview]
Message-ID: <20170611132424.GA15690@ns.kevlo.org> (raw)
In-Reply-To: <87y3szos2p.fsf@purkki.adurom.net>
On Sun, Jun 11, 2017 at 11:18:38AM +0300, Kalle Valo wrote:
>
> 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, 莊彥宣 wrote:
> >> Yes, the register 0x55c is for REG_USTIME_TSF.
> >> And 0x551 is for BCN_CTRL1.
> >>
> >>
> >> Acked-by: Yan-Hsuan, Chuang <yhchuang@realtek.com>
> >>
> >> 2017-05-19 23:02 GMT+08:00 Kevin Lo <kevlo@kevlo.org>:
> >>
> >> > 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 replied privately to me. I think he forgot to cc linux-wireless@.
> Yan-Hsuan or Larry, can you please resend the ack so that patchwork sees
> it?
>
> --
> Kalle Valo
next prev parent reply other threads:[~2017-06-11 13:24 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
2017-06-11 13:24 ` Kevin Lo [this message]
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=20170611132424.GA15690@ns.kevlo.org \
--to=kevlo@kevlo.org \
--cc=Larry.Finger@lwfinger.net \
--cc=kvalo@codeaurora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.