linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jszhang@marvell.com (Jisheng Zhang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 3/4] clk: berlin: bg2q: remove CLK_IGNORE_UNUSED flag for sdio clk
Date: Wed, 21 Oct 2015 18:08:56 +0800	[thread overview]
Message-ID: <20151021180856.217e11ea@xhacker> (raw)
In-Reply-To: <20151021095454.20687.98330@quantum>

Dear Michael,

On Wed, 21 Oct 2015 02:54:54 -0700
Michael Turquette <mturquette@baylibre.com> wrote:

> Quoting Michael Turquette (2015-10-21 02:30:39)
> > Quoting Jisheng Zhang (2015-10-20 04:16:46)  
> > > Since we have added the necessary two clks' properties in dts, we can
> > > remove the "sdio" clk's CLK_IGNORE_UNUSED flag now.
> > > 
> > > Signed-off-by: Jisheng Zhang <jszhang@marvell.com>  
> > 
> > Applied to clk-next.  
> 
> So the sdhci change was dropped from v2. Do you want me to Ack these
> instead so you can send them all together?

I'll send another patch to for the sdhci change. it doesn't matter even the
sdhci change delay a merge window because no functionality changes in the
sdhci commit.

It's better we firstly take these clk clean ups because it saves power a bit
and clean up the CLK_IGNORE_UNUSED flag.

Hi Sebastian,

What do you think?

Thanks,
Jisheng

  reply	other threads:[~2015-10-21 10:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-20 11:16 [PATCH v2 0/4] berlin sdhci clock clean up Jisheng Zhang
2015-10-20 11:16 ` [PATCH v2 1/4] ARM: dts: berlin: correct BG2Q's sdhci2 2nd clock Jisheng Zhang
2015-10-20 11:16 ` [PATCH v2 2/4] ARM: dts: berlin: add 2nd clock for BG2Q sdhci0 and sdhci1 Jisheng Zhang
2015-10-20 11:16 ` [PATCH v2 3/4] clk: berlin: bg2q: remove CLK_IGNORE_UNUSED flag for sdio clk Jisheng Zhang
2015-10-21  9:30   ` Michael Turquette
2015-10-21  9:54     ` Michael Turquette
2015-10-21 10:08       ` Jisheng Zhang [this message]
2015-10-20 11:16 ` [PATCH v2 4/4] clk: berlin: bg2: " Jisheng Zhang
2015-10-21  9:30   ` Michael Turquette

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=20151021180856.217e11ea@xhacker \
    --to=jszhang@marvell.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;
as well as URLs for NNTP newsgroup(s).