From: Stephen Boyd <sboyd@codeaurora.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
linux-clk@vger.kernel.org
Subject: Re: [PATCH 1/3] clk/ARM: delete the non-DT U8500 clock implementation
Date: Tue, 11 Aug 2015 16:45:52 -0700 [thread overview]
Message-ID: <20150811234552.GP2839@codeaurora.org> (raw)
In-Reply-To: <CACRpkdYdFAjRGMfsG4Kx=xNBACofcjFR3U1+P4U3yBmgQcFATQ@mail.gmail.com>
On 08/10, Linus Walleij wrote:
> On Mon, Aug 3, 2015 at 11:51 PM, Stephen Boyd <sboyd@codeaurora.org> wrote:
> > On 07/30, Linus Walleij wrote:
> >> This code is unused and not coming back. Let's kill it off.
> >>
> >> Cc: Ulf Hansson <ulf.hansson@linaro.org>
> >> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> >> ---
> >> Mike/Ulf: please ACK this so I can take this in through ARM
> >> SoC.
> >> ---
> >> drivers/clk/ux500/Makefile | 1 -
> >> drivers/clk/ux500/u8500_clk.c | 526 --------------------------------
> >
> > There's a patch in -next against this file.
> >
> > commit a162ca912cf792073b0b2450377fd1cd5d5c6cb5
> > Author: Stephen Boyd <sboyd@codeaurora.org>
> > Date: Fri Jun 19 15:00:46 2015 -0700
> >
> > clk: ux500: Remove clk.h and clkdev.h includes
> >
> > so I wonder why we need to take this patch through arm-soc? Would
> > an immutable branch from the clk tree work as well?
>
> No you can actually apply it in isolation. I was just collecting
> them in one spot for testing.
>
> Can you please apply this directly to the clk tree and
> fix any clashes?
Sure. Do we need to apply patches 2 and 3 too? I'm mostly trying
to avoid merge conflicts.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-08-11 23:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 13:19 [PATCH 1/3] clk/ARM: delete the non-DT U8500 clock implementation Linus Walleij
2015-08-03 21:51 ` Stephen Boyd
2015-08-10 8:46 ` Linus Walleij
2015-08-11 23:45 ` Stephen Boyd [this message]
2015-08-12 8:27 ` Linus Walleij
2015-08-12 11:26 ` Linus Walleij
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=20150811234552.GP2839@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linus.walleij@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=ulf.hansson@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.