From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] i.MX fixes for 4.14
Date: Mon, 16 Oct 2017 15:38:52 +0800 [thread overview]
Message-ID: <20171016073851.GA8320@x250> (raw)
The following changes since commit 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e:
Linux 4.14-rc1 (2017-09-16 15:47:51 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-fixes-4.14
for you to fetch changes up to 1c86c9dd82f859b474474a7fee0d5195da2c9c1d:
ARM: dts: imx7d: Invert legacy PCI irq mapping (2017-10-14 23:32:51 +0800)
----------------------------------------------------------------
i.MX fixes for 4.14:
- Fix the legacy PCI interrupt numbers for i.MX7. The numbers were
wrongly coded in an inverted order than what Reference Manual tells.
It causes problem for PCI devices using legacy interrupt.
----------------------------------------------------------------
Andrey Smirnov (1):
ARM: dts: imx7d: Invert legacy PCI irq mapping
arch/arm/boot/dts/imx7d.dtsi | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
next reply other threads:[~2017-10-16 7:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 7:38 Shawn Guo [this message]
2017-10-19 15:42 ` [GIT PULL] i.MX fixes for 4.14 Arnd Bergmann
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=20171016073851.GA8320@x250 \
--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 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).