From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Marc Zyngier <marc.zyngier@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Mark Rutland <mark.rutland@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PULL] clocksource/arch_timer: Errata workaround infrastructure rework
Date: Fri, 7 Apr 2017 16:27:26 +0200 [thread overview]
Message-ID: <20170407142726.GM2078@mai> (raw)
In-Reply-To: <20170407135921.17549-1-marc.zyngier@arm.com>
On Fri, Apr 07, 2017 at 02:59:21PM +0100, Marc Zyngier wrote:
> Hi Daniel,
>
> Please find below the pull request for the arm64 architected timer
> workaround infrastructure. As discussed on the list, the first 5
> patches are shared with the arm64 tree (and the whole branch is stable
> anyway).
>
Pulled, thanks.
-- Daniel
prev parent reply other threads:[~2017-04-07 14:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 13:59 [PULL] clocksource/arch_timer: Errata workaround infrastructure rework Marc Zyngier
2017-04-07 14:27 ` Daniel Lezcano [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=20170407142726.GM2078@mai \
--to=daniel.lezcano@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.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).