From: Stephen Boyd <sboyd@codeaurora.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: Fabio Estevam <fabio.estevam@nxp.com>,
Joshua Clayton <stillcompiling@gmail.com>,
Sascha Hauer <kernel@pengutronix.de>,
Michael Turquette <mturquette@baylibre.com>,
Ranjani Vaidyanathan <Ranjani.Vaidyanathan@nxp.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
"Charles.Kang" <Charles.Kang@advantech.com.tw>,
Shawn Guo <shawnguo@kernel.org>,
linux-clk@vger.kernel.org, Akshay Bhat <akshay.bhat@timesys.com>
Subject: Re: [PATCH 3/3] clk: imx6: Fix procedure to switch the parent of LDB_DI_CLK
Date: Tue, 18 Oct 2016 17:05:26 -0700 [thread overview]
Message-ID: <20161019000526.GR8871@codeaurora.org> (raw)
In-Reply-To: <CAOMZO5Ae_cB3BiqckAiOyaJPd2HWELkR8hVjEKHbY1nVOAeMxQ@mail.gmail.com>
On 10/18, Fabio Estevam wrote:
> Hi Stephen,
>
> On Tue, Oct 18, 2016 at 10:01 PM, Stephen Boyd <sboyd@codeaurora.org> wrote:
>
> > Urgh, sorry I missed this one and then we got too close to the
> > merge window to keep applying things and I was traveling for a
> > bit. Is this a bug that's urgent and needs to be fixed to keep
> > these boards working in the v4.9-rc series? Does it need to go
> > back to stable? The change is fairly large, so we might be able
> > to put it into clk-fixes for -rc2, but it would need some
> > justification and preferably a stable/fixes tag.
> >
> > Also, what about the other two patches in this series?
>
> Yesterday I resent this series based on linux-next, so if you could
> apply them to clk-next that would be great.
>
Ok that makes it easy. Thanks.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
WARNING: multiple messages have this Message-ID (diff)
From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] clk: imx6: Fix procedure to switch the parent of LDB_DI_CLK
Date: Tue, 18 Oct 2016 17:05:26 -0700 [thread overview]
Message-ID: <20161019000526.GR8871@codeaurora.org> (raw)
In-Reply-To: <CAOMZO5Ae_cB3BiqckAiOyaJPd2HWELkR8hVjEKHbY1nVOAeMxQ@mail.gmail.com>
On 10/18, Fabio Estevam wrote:
> Hi Stephen,
>
> On Tue, Oct 18, 2016 at 10:01 PM, Stephen Boyd <sboyd@codeaurora.org> wrote:
>
> > Urgh, sorry I missed this one and then we got too close to the
> > merge window to keep applying things and I was traveling for a
> > bit. Is this a bug that's urgent and needs to be fixed to keep
> > these boards working in the v4.9-rc series? Does it need to go
> > back to stable? The change is fairly large, so we might be able
> > to put it into clk-fixes for -rc2, but it would need some
> > justification and preferably a stable/fixes tag.
> >
> > Also, what about the other two patches in this series?
>
> Yesterday I resent this series based on linux-next, so if you could
> apply them to clk-next that would be great.
>
Ok that makes it easy. Thanks.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2016-10-19 0:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 14:36 [PATCH 1/3] clk: imx6: Mask mmdc_ch1 handshake for periph2_sel and mmdc_ch1_axi_podf Fabio Estevam
2016-09-16 14:36 ` Fabio Estevam
2016-09-16 14:36 ` [PATCH 2/3] clk: imx6: Make the LDB_DI0 and LDB_DI1 clocks read-only Fabio Estevam
2016-09-16 14:36 ` Fabio Estevam
2016-09-16 14:36 ` [PATCH 3/3] clk: imx6: Fix procedure to switch the parent of LDB_DI_CLK Fabio Estevam
2016-09-16 14:36 ` Fabio Estevam
2016-09-23 22:12 ` Fabio Estevam
2016-09-23 22:12 ` Fabio Estevam
2016-10-19 0:01 ` Stephen Boyd
2016-10-19 0:01 ` Stephen Boyd
2016-10-19 0:03 ` Fabio Estevam
2016-10-19 0:03 ` Fabio Estevam
2016-10-19 0:05 ` Stephen Boyd [this message]
2016-10-19 0:05 ` Stephen Boyd
2016-10-19 23:18 ` Fabio Estevam
2016-10-19 23:18 ` Fabio Estevam
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=20161019000526.GR8871@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=Charles.Kang@advantech.com.tw \
--cc=Ranjani.Vaidyanathan@nxp.com \
--cc=akshay.bhat@timesys.com \
--cc=fabio.estevam@nxp.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=p.zabel@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=stillcompiling@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.