From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM/clk: move the ICST library to drivers/clk
Date: Wed, 5 Apr 2017 15:03:58 -0700 [thread overview]
Message-ID: <20170405220358.GI7065@codeaurora.org> (raw)
In-Reply-To: <CACRpkdY2wvae2n-vBmkXwh6rhVWP_pZddJ3e5BZzQO9q5OVzSA@mail.gmail.com>
On 03/28, Linus Walleij wrote:
> On Sat, Mar 18, 2017 at 9:59 AM, Linus Walleij <linus.walleij@linaro.org> wrote:
>
> > This moves the ICST clock divider helper library from
> > arch/arm/common to drivers/clk/versatile so it is maintained
> > with the other clock drivers.
> >
> > We keep the structure as a helper library intact and do not
> > fuse it with the clk-icst.c Versatile ICST clock driver: there
> > may be other users out there that need to use this library for
> > their clocking, and then it will be helpful to keep the
> > library contained. (The icst.[c|h] files could just be moved
> > to drivers/clk/lib or a similar location to share the library.)
> >
> > Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
>
> CLK maintainers: could you ACK this so that I can ask the ARM
> SoC tree to pull in these two patches?
>
> Or do you prefer to take all patches in the CLK tree so I should
> ask the ARM people to ACK it?
>
Either way is fine.
Acked-by: Stephen Boyd <sboyd@codeaurora.org>
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2017-04-05 22:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-18 8:59 [PATCH 0/2] move the ICST library to common clocks Linus Walleij
2017-03-18 8:59 ` [PATCH 1/2] ARM: plat-versatile: remove stale clock header Linus Walleij
2017-03-18 8:59 ` [PATCH 2/2] ARM/clk: move the ICST library to drivers/clk Linus Walleij
2017-03-28 21:04 ` Linus Walleij
2017-04-05 22:03 ` Stephen Boyd [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=20170405220358.GI7065@codeaurora.org \
--to=sboyd@codeaurora.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).