From: Linus Walleij <linus.walleij@linaro.org>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Marc Zyngier <marc.zyngier@arm.com>,
John Stultz <john.stultz@linaro.org>,
Stephen Boyd <sboyd@codeaurora.org>
Subject: Re: [PATCH 4/7] clocksource: Rename CLOCKSOURCE_ACPI_DECLARE
Date: Sun, 28 May 2017 15:50:23 +0200 [thread overview]
Message-ID: <CACRpkdbjSFH+RLudFqKA6oPQtrT4eb3L2uu4X8R-2m+CT-_bWw@mail.gmail.com> (raw)
In-Reply-To: <1495879129-28109-4-git-send-email-daniel.lezcano@linaro.org>
On Sat, May 27, 2017 at 11:58 AM, Daniel Lezcano
<daniel.lezcano@linaro.org> wrote:
> The macro name is now renamed to 'TIMER_ACPI_DECLARE' for consistency
> with the CLOCKSOURCE_OF_DECLARE => TIMER_OF_DECLARE change.
>
> Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
Yours,
Linus Walleij
next prev parent reply other threads:[~2017-05-28 13:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-27 9:58 [PATCH 1/7] Revert "clockevents: Add a clkevt-of mechanism like clksrc-of" Daniel Lezcano
2017-05-27 9:58 ` [PATCH 4/7] clocksource: Rename CLOCKSOURCE_ACPI_DECLARE Daniel Lezcano
2017-05-28 13:50 ` Linus Walleij [this message]
2017-05-27 9:58 ` [PATCH 5/7] clocksource: Rename clksrc Daniel Lezcano
2017-05-28 13:51 ` Linus Walleij
2017-05-27 9:58 ` [PATCH 6/7] clocksource: Rename CLKSRC_OF to TIMER_OF Daniel Lezcano
2017-05-28 3:00 ` Shawn Guo
2017-05-28 9:18 ` Daniel Lezcano
2017-05-28 13:52 ` Linus Walleij
2017-05-31 8:24 ` Krzysztof Kozlowski
2017-05-27 9:58 ` [PATCH 7/7] clocksource: Rename CLKSRC_ACPI Daniel Lezcano
2017-05-28 13:52 ` Linus Walleij
[not found] ` <1495879129-28109-2-git-send-email-daniel.lezcano@linaro.org>
2017-05-29 8:02 ` [PATCH 2/7] clocksource: Rename CLOCKSOURCE_OF_DECLARE Mason
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=CACRpkdbjSFH+RLudFqKA6oPQtrT4eb3L2uu4X8R-2m+CT-_bWw@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=daniel.lezcano@linaro.org \
--cc=john.stultz@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=sboyd@codeaurora.org \
--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;
as well as URLs for NNTP newsgroup(s).