From: Stefan Agner <stefan@agner.ch>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: shawnguo@kernel.org, kernel@pengutronix.de, aisheng.dong@nxp.com,
fabio.estevam@nxp.com, robh+dt@kernel.org, mark.rutland@arm.com,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] clk: imx7d: fix USDHC NAND clock
Date: Wed, 19 Apr 2017 09:23:44 -0700 [thread overview]
Message-ID: <9f0b9e83bc2a46bacb323d3ff2cfcf64@agner.ch> (raw)
In-Reply-To: <20170419161435.GA7065@codeaurora.org>
On 2017-04-19 09:14, Stephen Boyd wrote:
> On 04/10, Stefan Agner wrote:
>> The USDHC NAND root clock is not gated by any CCM clock gate. Remove
>> the bogus gate definition.
>>
>> Signed-off-by: Stefan Agner <stefan@agner.ch>
>> ---
>
> Can this be applied? It's followed by a dtsi change and there is
> zero information about if the two depend on each other. Please
> add cover letters for these sorts of things in the future
> indicating how you expect merging to work.
This can be merged. The two changes are independent.
They look kind of dependent, but really aren't since
IMX7D_NAND_USDHC_BUS_ROOT_CLK is still in the init_on list. Should have
explicitly mentioned that, sorry about that.
--
Stefan
next prev parent reply other threads:[~2017-04-19 16:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 21:00 [PATCH v2 1/2] clk: imx7d: fix USDHC NAND clock Stefan Agner
2017-04-10 21:00 ` [PATCH v2 2/2] ARM: dts: imx7: add USDHC NAND and IPG clock to SDHC instances Stefan Agner
2017-04-11 20:00 ` Dong Aisheng
2017-05-15 1:53 ` Shawn Guo
[not found] ` <20170410210015.1620-1-stefan-XLVq0VzYD2Y@public.gmane.org>
2017-04-11 19:59 ` [PATCH v2 1/2] clk: imx7d: fix USDHC NAND clock Dong Aisheng
2017-04-19 16:14 ` Stephen Boyd
2017-04-19 16:23 ` Stefan Agner [this message]
[not found] ` <9f0b9e83bc2a46bacb323d3ff2cfcf64-XLVq0VzYD2Y@public.gmane.org>
2017-04-19 16:44 ` Stephen Boyd
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=9f0b9e83bc2a46bacb323d3ff2cfcf64@agner.ch \
--to=stefan@agner.ch \
--cc=aisheng.dong@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=shawnguo@kernel.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).