From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: i.MX fixes for 4.18, round 3
Date: Thu, 19 Jul 2018 15:48:46 +0800 [thread overview]
Message-ID: <20180719074844.GW4576@dragon> (raw)
The following changes since commit 2ceb2780b790b74bc408a949f6aedbad8afa693e:
ARM: imx_v4_v5_defconfig: Select ULPI support (2018-07-03 21:12:04 +0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-fixes-4.18-3
for you to fetch changes up to de2d9b5284bcb5c159c5882ac69f6bfd4dec7c67:
soc: imx: gpc: restrict register range for regmap access (2018-07-19 10:24:00 +0800)
----------------------------------------------------------------
i.MX fixes for 4.18, round 3:
- Restrict GPC driver on register range that is accessible by regmap,
so that we can avoid user space from triggering imprecise external
abort exception.
----------------------------------------------------------------
Anson Huang (1):
soc: imx: gpc: restrict register range for regmap access
drivers/soc/imx/gpc.c | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
next reply other threads:[~2018-07-19 7:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 7:48 Shawn Guo [this message]
2018-07-19 22:05 ` i.MX fixes for 4.18, round 3 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=20180719074844.GW4576@dragon \
--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).