From: Shawn Guo <shawnguo@kernel.org>
To: Stefan Agner <stefan@agner.ch>
Cc: galak@codeaurora.org, ijc+devicetree@hellion.org.uk,
mark.rutland@arm.com, pawel.moll@arm.com, robh+dt@kernel.org,
Li.Xiubo@freescale.com, zidan.wang@freescale.com,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@pengutronix.de, mturquette@baylibre.com,
sboyd@codeaurora.org
Subject: Re: [PATCH 3/3] ARM: dts: vf610: add remaining SAI instaces
Date: Thu, 28 Jan 2016 09:53:08 +0800 [thread overview]
Message-ID: <20160128015308.GB9070@tiger> (raw)
In-Reply-To: <7c3b0b28706f2bf1cf656c7dc2daf31d@agner.ch>
On Wed, Jan 27, 2016 at 04:31:48PM -0800, Stefan Agner wrote:
> Hi Shawn,
>
> The rest of the patchset has been applied during rc phase of v4.4, I
> guess this one was scheduled for the next release (v4.5). However, I
> just realized that this seemed to have slipped through...
Sorry, Stefan. If I can get a ping from you before v4.5 merge window
closes, we might be able to catch up with v4.5.
Queued it up for v4.6.
Shawn
WARNING: multiple messages have this Message-ID (diff)
From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] ARM: dts: vf610: add remaining SAI instaces
Date: Thu, 28 Jan 2016 09:53:08 +0800 [thread overview]
Message-ID: <20160128015308.GB9070@tiger> (raw)
In-Reply-To: <7c3b0b28706f2bf1cf656c7dc2daf31d@agner.ch>
On Wed, Jan 27, 2016 at 04:31:48PM -0800, Stefan Agner wrote:
> Hi Shawn,
>
> The rest of the patchset has been applied during rc phase of v4.4, I
> guess this one was scheduled for the next release (v4.5). However, I
> just realized that this seemed to have slipped through...
Sorry, Stefan. If I can get a ping from you before v4.5 merge window
closes, we might be able to catch up with v4.5.
Queued it up for v4.6.
Shawn
next prev parent reply other threads:[~2016-01-28 1:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-18 4:05 [PATCH 1/3] ARM: imx: clk-vf610: fix SAI clock tree Stefan Agner
2015-10-18 4:05 ` Stefan Agner
2015-10-18 4:05 ` [PATCH 2/3] ARM: dts: vf610: fix clock definition for SAI2 Stefan Agner
2015-10-18 4:05 ` Stefan Agner
2015-10-18 4:05 ` Stefan Agner
2015-11-23 3:04 ` Shawn Guo
2015-11-23 3:04 ` Shawn Guo
2015-11-23 3:04 ` Shawn Guo
2015-10-18 4:05 ` [PATCH 3/3] ARM: dts: vf610: add remaining SAI instaces Stefan Agner
2015-10-18 4:05 ` Stefan Agner
2016-01-28 0:31 ` Stefan Agner
2016-01-28 0:31 ` Stefan Agner
2016-01-28 1:53 ` Shawn Guo [this message]
2016-01-28 1:53 ` Shawn Guo
2016-01-28 1:52 ` Stefan Agner
2016-01-28 1:52 ` Stefan Agner
2015-11-19 1:58 ` [PATCH 1/3] ARM: imx: clk-vf610: fix SAI clock tree Stefan Agner
2015-11-19 1:58 ` Stefan Agner
2015-11-23 1:46 ` Shawn Guo
2015-11-23 1:46 ` Shawn Guo
2015-11-30 20:55 ` Stephen Boyd
2015-11-30 20:55 ` Stephen Boyd
2015-11-30 20:55 ` Stephen Boyd
2015-11-30 20:55 ` Stephen Boyd
2015-12-02 5:24 ` Shawn Guo
2015-12-02 5:24 ` 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=20160128015308.GB9070@tiger \
--to=shawnguo@kernel.org \
--cc=Li.Xiubo@freescale.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--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=mturquette@baylibre.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=stefan@agner.ch \
--cc=zidan.wang@freescale.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.