From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: imx: fixes for 4.2, 2nd round
Date: Tue, 28 Jul 2015 14:04:37 +0800 [thread overview]
Message-ID: <20150728060437.GF12927@tiger> (raw)
The following changes since commit d438462c20a300139c2e5e65b96cadaa21b58d9a:
ARM: imx6: gpc: always enable PU domain if CONFIG_PM is not set (2015-07-08 22:52:08 +0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-fixes-4.2-2
for you to fetch changes up to e053f96b1a00022b4e2c7ceb7ac0229646626507:
ARM: dts: i.MX35: Fix can support. (2015-07-25 11:35:08 +0800)
----------------------------------------------------------------
The i.MX fixes for 4.2, 2nd round:
- Add the required second clock for i.MX35 FlexCAN in device tree,
so that the device can be probed by kernel successfully.
----------------------------------------------------------------
Denis Carikli (1):
ARM: dts: i.MX35: Fix can support.
arch/arm/boot/dts/imx35.dtsi | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
next reply other threads:[~2015-07-28 6:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 6:04 Shawn Guo [this message]
2015-07-28 10:32 ` [GIT PULL] ARM: imx: fixes for 4.2, 2nd round Olof Johansson
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=20150728060437.GF12927@tiger \
--to=shawnguo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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 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.