From: benh@kernel.crashing.org (Benjamin Herrenschmidt)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/4] drivers/clocksource/moxart: Refactor enable/disable
Date: Wed, 20 Jul 2016 18:22:39 +1000 [thread overview]
Message-ID: <1469002959.8568.102.camel@kernel.crashing.org> (raw)
In-Reply-To: <20160720081400.GA2705@linaro.org>
On Wed, 2016-07-20 at 10:14 +0200, Daniel Lezcano wrote:
>
> actually I forgot to include your patchset which is no longer applying?
> correctly and the conflicts are not trivials (easy but not trivial). It is a?
> bit late to ask for a last minute pull. Sorry for that.
>
> Please respin and resend your patchset, I will include it in my tree?
> immediately so that won't happen again. The patch 1/4 is no longer needed.
>
> If there is a really urgent need of this series, please let us know and?
> Thomas can take a decision accordingly.
I think all the other bits to have basic support for the Aspeed SoC are
in except this one, so it would be nice for this to make the merge
window...
Cheers,
Ben.
next prev parent reply other threads:[~2016-07-20 8:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 12:32 [PATCH 0/4] clocksource: Add support for Aspeed timer Joel Stanley
2016-05-09 12:32 ` [PATCH 1/4] drivers/clocksouree/moxart: Add kbuild symbol Joel Stanley
2016-05-09 12:32 ` [PATCH 2/4] drivers/clocksource/moxart: Refactor enable/disable Joel Stanley
2016-05-10 11:06 ` Joel Stanley
2016-05-10 13:04 ` Daniel Lezcano
2016-07-20 5:17 ` Joel Stanley
2016-07-20 8:14 ` Daniel Lezcano
2016-07-20 8:22 ` Benjamin Herrenschmidt [this message]
2016-05-09 12:32 ` [PATCH 3/4] drivers/clocksource/moxart: Use struct to hold state Joel Stanley
2016-05-09 12:32 ` [PATCH 4/4] drivers/clocksource/moxart: Add Aspeed support Joel Stanley
2016-05-09 20:36 ` Rob Herring
2016-05-10 10:22 ` [PATCH 0/4] clocksource: Add support for Aspeed timer 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=1469002959.8568.102.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--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).