linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Turquette, Mike" <mturquette@ti.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Arnd Bergmann <arnd@arndb.de>,
	linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
	Olof Johansson <olof@lixom.net>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: linux-next: manual merge of the akpm tree with the arm-soc tree
Date: Mon, 14 May 2012 14:57:56 -0700	[thread overview]
Message-ID: <CAJOA=zOvLak8ua+0dJTvgOuhF=TrpXaXZt+UXcn9-EEnh1+KBA@mail.gmail.com> (raw)
In-Reply-To: <20120514192404.91f9477851ad8485a2112973@canb.auug.org.au>

On Mon, May 14, 2012 at 2:24 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Andrew,
>
> Today's linux-next merge of the akpm tree got a conflict in
> drivers/clk/Kconfig between commit d269b974e32c ("clk: remove
> COMMON_CLK_DISABLE_UNUSED") from the arm-soc tree and commit "clk: remove
> redundant depends on from drivers/Kconfig" from the akpm tree.
>
> I fixed it up (see below) and can carry the fix as necessary.

Hi Stephen,

The fix-up is correct.

Thanks,
Mike

> --
> Cheers,
> Stephen Rothwell                    sfr@canb.auug.org.au
>
> diff --cc drivers/clk/Kconfig
> index 4864407,4f10a21..0000000
> --- a/drivers/clk/Kconfig
> +++ b/drivers/clk/Kconfig
> @@@ -23,9 -22,18 +23,8 @@@ config COMMON_CL
>  menu "Common Clock Framework"
>        depends on COMMON_CLK
>
>  -config COMMON_CLK_DISABLE_UNUSED
>  -      bool "Disabled unused clocks at boot"
>  -      ---help---
>  -        Traverses the entire clock tree and disables any clocks that are
>  -        enabled in hardware but have not been enabled by any device drivers.
>  -        This saves power and keeps the software model of the clock in line
>  -        with reality.
>  -
>  -        If in doubt, say "N".
>  -
>  config COMMON_CLK_DEBUG
>        bool "DebugFS representation of clock tree"
> -       depends on COMMON_CLK
>        select DEBUG_FS
>        ---help---
>          Creates a directory hierchy in debugfs for visualizing the clk
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>

  reply	other threads:[~2012-05-14 21:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-14  9:24 linux-next: manual merge of the akpm tree with the arm-soc tree Stephen Rothwell
2012-05-14 21:57 ` Turquette, Mike [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-06-21  7:36 Stephen Rothwell
2013-06-21  7:33 Stephen Rothwell
2013-03-12  3:47 Stephen Rothwell
2013-03-12  6:25 ` Andrew Lunn
2013-03-12 11:12   ` Jason Cooper
2013-03-12 11:37     ` Olof Johansson
2013-03-12 11:53       ` Jason Cooper
2013-03-12 12:48         ` Arnd Bergmann
2013-03-12 13:32           ` Jason Cooper
2013-03-12 20:20         ` Andrew Morton
2012-05-17  7:18 Stephen Rothwell
2012-02-29  6:21 Stephen Rothwell
2012-02-29  6:32 ` Yong Zhang
2012-02-29  6:54   ` Haojian Zhuang
2012-02-29  7:11     ` Stephen Rothwell

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='CAJOA=zOvLak8ua+0dJTvgOuhF=TrpXaXZt+UXcn9-EEnh1+KBA@mail.gmail.com' \
    --to=mturquette@ti.com \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=sfr@canb.auug.org.au \
    /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).