From: maxime.ripard@bootlin.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: allwinner: h6: restore the usage of CCU slice macros
Date: Mon, 23 Apr 2018 09:47:34 +0200 [thread overview]
Message-ID: <20180423074734.rb4ddxtymbxtrpzp@flea> (raw)
In-Reply-To: <1524466728.25095.0.camel@aosc.io>
On Mon, Apr 23, 2018 at 02:58:48PM +0800, Icenowy Zheng wrote:
> ? 2018-04-03?? 21:40 +0800?Icenowy Zheng???
> > As the definition of CCU slice macros are already merged into the
> > source
> > tree, restore the usage of the macros now.
>
> Maxime, could you check this patch and pick it?
Applied, thanks!
maxime
--
Maxime Ripard, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180423/f58ca7d1/attachment.sig>
prev parent reply other threads:[~2018-04-23 7:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-03 13:40 [PATCH] arm64: allwinner: h6: restore the usage of CCU slice macros Icenowy Zheng
2018-04-23 6:58 ` Icenowy Zheng
2018-04-23 7:47 ` Maxime Ripard [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=20180423074734.rb4ddxtymbxtrpzp@flea \
--to=maxime.ripard@bootlin.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