From: Shawn Guo <shawnguo2@vip.163.com>
To: Vladimir Zapolskiy <vz@mleia.com>
Cc: "Shawn Guo" <shawnguo@kernel.org>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Michael Turquette" <mturquette@baylibre.com>,
"Stephen Boyd" <sboyd@codeaurora.org>,
"Fabio Estevam" <fabio.estevam@nxp.com>,
linux-arm-kernel@lists.infradead.org,
"Sascha Hauer" <kernel@pengutronix.de>,
linux-clk@vger.kernel.org
Subject: Re: [PATCH v2 0/4] ARM: imx31: clock initialization fixes
Date: Tue, 1 Nov 2016 16:50:09 +0800 [thread overview]
Message-ID: <20161101085009.GA23220@tiger> (raw)
In-Reply-To: <1474848223-19728-1-git-send-email-vz@mleia.com>
On Mon, Sep 26, 2016 at 03:03:39AM +0300, Vladimir Zapolskiy wrote:
> Vladimir Zapolskiy (4):
> ARM: dts: imx31: fix clock control module interrupts description
> ARM: dts: imx31: move CCM device node to AIPS2 bus devices
> clk: imx31: fix rewritten input argument of mx31_clocks_init()
> ARM: clk: imx31: properly init clocks for machines with DT
Applied all, thanks.
WARNING: multiple messages have this Message-ID (diff)
From: shawnguo2@vip.163.com (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/4] ARM: imx31: clock initialization fixes
Date: Tue, 1 Nov 2016 16:50:09 +0800 [thread overview]
Message-ID: <20161101085009.GA23220@tiger> (raw)
In-Reply-To: <1474848223-19728-1-git-send-email-vz@mleia.com>
On Mon, Sep 26, 2016 at 03:03:39AM +0300, Vladimir Zapolskiy wrote:
> Vladimir Zapolskiy (4):
> ARM: dts: imx31: fix clock control module interrupts description
> ARM: dts: imx31: move CCM device node to AIPS2 bus devices
> clk: imx31: fix rewritten input argument of mx31_clocks_init()
> ARM: clk: imx31: properly init clocks for machines with DT
Applied all, thanks.
next prev parent reply other threads:[~2016-11-01 8:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-26 0:03 [PATCH v2 0/4] ARM: imx31: clock initialization fixes Vladimir Zapolskiy
2016-09-26 0:03 ` Vladimir Zapolskiy
2016-09-26 0:03 ` [PATCH v2 1/4] ARM: dts: imx31: fix clock control module interrupts description Vladimir Zapolskiy
2016-09-26 0:03 ` Vladimir Zapolskiy
2016-09-26 0:03 ` [PATCH v2 2/4] ARM: dts: imx31: move CCM device node to AIPS2 bus devices Vladimir Zapolskiy
2016-09-26 0:03 ` Vladimir Zapolskiy
2016-09-26 6:36 ` Uwe Kleine-König
2016-09-26 6:36 ` Uwe Kleine-König
2016-09-26 0:03 ` [PATCH v2 3/4] clk: imx31: fix rewritten input argument of mx31_clocks_init() Vladimir Zapolskiy
2016-09-26 0:03 ` Vladimir Zapolskiy
2016-09-26 6:23 ` Uwe Kleine-König
2016-09-26 6:23 ` Uwe Kleine-König
2016-10-25 20:36 ` Stephen Boyd
2016-10-25 20:36 ` Stephen Boyd
2016-09-26 0:03 ` [PATCH v2 4/4] ARM: clk: imx31: properly init clocks for machines with DT Vladimir Zapolskiy
2016-09-26 0:03 ` Vladimir Zapolskiy
2016-10-25 20:37 ` Stephen Boyd
2016-10-25 20:37 ` Stephen Boyd
2016-10-23 12:28 ` [PATCH v2 0/4] ARM: imx31: clock initialization fixes Shawn Guo
2016-10-23 12:28 ` Shawn Guo
2016-10-25 20:37 ` Stephen Boyd
2016-10-25 20:37 ` Stephen Boyd
2016-11-01 8:50 ` Shawn Guo [this message]
2016-11-01 8:50 ` Shawn Guo
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=20161101085009.GA23220@tiger \
--to=shawnguo2@vip.163.com \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.org \
--cc=shawnguo@kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
--cc=vz@mleia.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.