From: Stephen Boyd <sboyd@codeaurora.org>
To: Andi Shyti <andi.shyti@samsung.com>
Cc: linux-samsung-soc@vger.kernel.org,
Sangbeom Kim <sbkim73@samsung.com>,
Krzysztof Kozlowski <k.kozlowski@samsung.com>,
Michael Turquette <mturquette@baylibre.com>,
linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
Andi Shyti <andi@etezian.org>,
Yadwinder Singh Brar <yadi.brar01@gmail.com>,
Jaehoon Chung <jh80.chung@samsung.com>
Subject: Re: [PATCH v3 1/4] clk: s2mps11: merge two for loops in one
Date: Fri, 29 Jan 2016 16:34:00 -0800 [thread overview]
Message-ID: <20160130003400.GH12841@codeaurora.org> (raw)
In-Reply-To: <1453284864-8082-2-git-send-email-andi.shyti@samsung.com>
On 01/20, Andi Shyti wrote:
> the driver already loops once, there is no reason to loop again
> for a different purpose. Merge the second loop into the first.
>
> Signed-off-by: Andi Shyti <andi.shyti@samsung.com>
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2016-01-30 0:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 10:14 [PATCH v3 0/4] s2mps11 clock driver refactoring Andi Shyti
2016-01-20 10:14 ` [PATCH v3 1/4] clk: s2mps11: merge two for loops in one Andi Shyti
2016-01-21 0:20 ` Krzysztof Kozlowski
2016-01-30 0:34 ` Stephen Boyd [this message]
2016-01-20 10:14 ` [PATCH v3 2/4] clk: s2mps11: allocate only one structure for clock init Andi Shyti
2016-01-21 0:23 ` Krzysztof Kozlowski
2016-01-30 0:34 ` Stephen Boyd
2016-01-20 10:14 ` [PATCH v3 3/4] clk: s2mps11: remove redundant static variables declaration Andi Shyti
2016-01-21 0:29 ` Krzysztof Kozlowski
2016-01-30 0:34 ` Stephen Boyd
2016-01-20 10:14 ` [PATCH v3 4/4] clk: s2mps11: remove redundant code Andi Shyti
2016-01-21 0:29 ` Krzysztof Kozlowski
2016-01-30 0:34 ` Stephen Boyd
2016-01-21 0:18 ` [PATCH v3 0/4] s2mps11 clock driver refactoring Krzysztof Kozlowski
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=20160130003400.GH12841@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=andi.shyti@samsung.com \
--cc=andi@etezian.org \
--cc=jh80.chung@samsung.com \
--cc=k.kozlowski@samsung.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sbkim73@samsung.com \
--cc=yadi.brar01@gmail.com \
/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.