From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Andrew Jeffery <andrew@aj.id.au>
Cc: linux-kernel@vger.kernel.org, robh+dt@kernel.org,
mark.rutland@arm.com, tglx@linutronix.de, joel@jms.id.au,
devicetree@vger.kernel.org, ryan_chen@aspeedtech.com
Subject: Re: [PATCH] clocksource: moxart: Add AST2500 compatible string
Date: Thu, 25 May 2017 22:28:08 +0200 [thread overview]
Message-ID: <20170525202808.GA9501@mai> (raw)
In-Reply-To: <20170516075840.23130-1-andrew@aj.id.au>
On Tue, May 16, 2017 at 03:58:40PM +0800, Andrew Jeffery wrote:
> Also clean up space-before-tab issues in the documentation.
Andrew,
I reworked the patch to apply to the changes Linus did recently to convert to
the fttrm010 driver.
Please have a look at:
https://git.linaro.org/people/daniel.lezcano/linux.git/commit/?h=clockevents/4.13&id=3ca904162ffdd72f4fad3ab731fc94a12c50f682
Shouldn't the compatible string be:
"aspeed,ast2400-timer", "faraday,fttmr010"
"aspeed,ast2500-timer", "faraday,fttmr010"
-- Daniel
next prev parent reply other threads:[~2017-05-25 20:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 7:58 [PATCH] clocksource: moxart: Add AST2500 compatible string Andrew Jeffery
2017-05-16 10:03 ` Joel Stanley
2017-05-23 0:07 ` Rob Herring
2017-05-25 20:28 ` Daniel Lezcano [this message]
2017-05-26 1:12 ` Andrew Jeffery
2017-05-26 8:48 ` [PATCH] clocksource/drivers/fttmr010: Fix aspeed-2500 initialization Daniel Lezcano
2017-05-28 13:56 ` Linus Walleij
2017-05-29 6:05 ` Andrew Jeffery
2017-05-29 7:45 ` Daniel Lezcano
2017-05-30 4:35 ` Joel Stanley
2017-05-28 14:00 ` [PATCH] clocksource: moxart: Add AST2500 compatible string Linus Walleij
2017-05-28 13:59 ` Linus Walleij
2017-05-28 18:27 ` Daniel Lezcano
2017-05-30 7:44 ` Linus Walleij
2017-05-30 8:54 ` Daniel Lezcano
2017-05-30 9:53 ` Linus Walleij
2017-05-30 10:03 ` Daniel Lezcano
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=20170525202808.GA9501@mai \
--to=daniel.lezcano@linaro.org \
--cc=andrew@aj.id.au \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=ryan_chen@aspeedtech.com \
--cc=tglx@linutronix.de \
/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