From: Will Deacon <will.deacon@arm.com>
To: Ding Tianhong <dingtianhong@huawei.com>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
marc.zyngier@arm.com, catalin.marinas@arm.com,
stuart.yoder@nxp.com, linuxarm@huawei.com, oss@buserror.net,
shawnguo@kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v6 0/4] arm64: arch_timer: Add workaround for hisilicon-161601 erratum
Date: Fri, 6 Jan 2017 12:27:39 +0000 [thread overview]
Message-ID: <20170106122739.GA20796@arm.com> (raw)
In-Reply-To: <e518ab78-4093-0bc9-fe68-e7da25fd5644@huawei.com>
On Fri, Jan 06, 2017 at 11:41:28AM +0800, Ding Tianhong wrote:
> Please help reviewing the new version, I think it is nearly close to the
> final solution and it is very important to our chip or something else chip
> has similar erratum. If there is any dissatisfaction, please inform me
> and I will fix it. :)
It looks fine to me, but I don't maintain the arch timer driver!
Will
prev parent reply other threads:[~2017-01-06 12:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 5:31 [PATCH v6 0/4] arm64: arch_timer: Add workaround for hisilicon-161601 erratum Ding Tianhong
2017-01-05 5:31 ` [PATCH v6 1/4] arm64: arch_timer: Add device tree binding " Ding Tianhong
2017-01-05 5:31 ` [PATCH v6 2/4] arm64: arch_timer: Introduce a generic erratum handing mechanism for fsl-a008585 Ding Tianhong
[not found] ` <1483594317-10732-1-git-send-email-dingtianhong-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2017-01-05 5:31 ` [PATCH v6 3/4] arm64: arch_timer: Work around Erratum Hisilicon-161601 Ding Tianhong
2017-01-06 14:49 ` Marc Zyngier
2017-01-07 2:36 ` Ding Tianhong
2017-01-05 5:31 ` [PATCH v6 4/4] arm64: arch timer: Add timer erratum property for Hip05-d02 and Hip06-d03 Ding Tianhong
2017-01-06 3:41 ` [PATCH v6 0/4] arm64: arch_timer: Add workaround for hisilicon-161601 erratum Ding Tianhong
2017-01-06 12:27 ` Will Deacon [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=20170106122739.GA20796@arm.com \
--to=will.deacon@arm.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=dingtianhong@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linuxarm@huawei.com \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=oss@buserror.net \
--cc=shawnguo@kernel.org \
--cc=stuart.yoder@nxp.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).