From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 3/5] arm64: arch_timer: Work around QorIQ Erratum A-008585
Date: Mon, 12 Sep 2016 12:44:07 +0100 [thread overview]
Message-ID: <20160912114406.GG23211@arm.com> (raw)
In-Reply-To: <20160912113615.GA20804@leverpostej>
On Mon, Sep 12, 2016 at 12:36:15PM +0100, Mark Rutland wrote:
> The changes in arm64's <asm/arch_timer.h> are going to conflict with
> some cleanup [1,2] that just landed in the arm64 for-next/core branch.
>
> Could you please rebase atop of that?
Well, we should figure out what tree this is going through first. There
are a mixture of arm, arm64, driver and dts changes here and not all
of it is carrying the appropriate acks for me to queue it.
Will
next prev parent reply other threads:[~2016-09-12 11:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-10 1:03 [PATCH v5 1/5] arm64: arch_timer: Add device tree binding for A-008585 erratum Scott Wood
2016-09-10 1:03 ` [PATCH v5 2/5] arm64: dts: Add timer erratum property for LS2080A and LS1043A Scott Wood
2016-09-10 1:03 ` [PATCH v5 3/5] arm64: arch_timer: Work around QorIQ Erratum A-008585 Scott Wood
2016-09-12 11:36 ` Mark Rutland
2016-09-12 11:44 ` Will Deacon [this message]
2016-09-12 12:30 ` Mark Rutland
2016-09-12 12:59 ` Mark Rutland
2016-09-12 13:07 ` Marc Zyngier
2016-09-19 4:31 ` Scott Wood
2016-09-19 16:55 ` Mark Rutland
2016-09-19 4:28 ` Scott Wood
2016-09-19 7:44 ` Arnd Bergmann
2016-09-20 12:52 ` Shawn Guo
2016-09-19 4:41 ` Scott Wood
2016-09-19 16:52 ` Mark Rutland
2016-09-19 17:01 ` Scott Wood
2016-09-19 17:07 ` Mark Rutland
2016-09-19 19:16 ` Scott Wood
2016-09-20 9:35 ` Mark Rutland
2016-09-22 8:34 ` Scott Wood
2016-09-10 1:03 ` [PATCH v5 4/5] arm/arm64: arch_timer: Use archdata to indicate vdso suitability Scott Wood
2016-09-10 1:03 ` [PATCH v5 5/5] arm64: arch_timer: Add command line parameter for A-008585 Scott Wood
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=20160912114406.GG23211@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).