From: patrice.chotard@st.com (Patrice Chotard)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL v3] STi SoC changes for v4.8
Date: Mon, 11 Jul 2016 09:41:17 +0200 [thread overview]
Message-ID: <57834D9D.4070900@st.com> (raw)
Hi Olof, Arnd and Kevin,
Please consider this first round of STi SoC updates for v4.8:
The following changes since commit 5edb56491d4812c42175980759da53388e5d86f5:
Linux 4.7-rc3 (2016-06-12 07:20:35 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/pchotard/sti.git
tags/sti-soc-for-v4.8
for you to fetch changes up to 7b8e0188fa717cd9abc4fb52587445b421835c2a:
ARM: sti: Implement dummy L2 cache's write_sec (2016-07-11 09:15:44
+0200)
----------------------------------------------------------------
Highlights:
-----------
- Add a dummy L2 cache's write_sec callback as in non secure mode execution,
we can't get access to L2 cache secure registers
- Cosmetics change, in case of dump_stack, update the hardware name with a
more generic for the STi SoCs family
----------------------------------------------------------------
Patrice Chotard (1):
ARM: sti: Implement dummy L2 cache's write_sec
Peter Griffin (1):
ARM: STi: Update machine _namestr to be more generic.
arch/arm/mach-sti/board-dt.c | 11 ++++++++++-
1 file changed, 10 insertions(+), 1 deletion(-)
WARNING: multiple messages have this Message-ID (diff)
From: Patrice Chotard <patrice.chotard@st.com>
To: Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
Kevin Hilman <khilman@baylibre.com>, <arm@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"open list:ARM/STI ARCHITECTURE" <kernel@stlinux.com>
Cc: Peter Griffin <peter.griffin@linaro.org>
Subject: [GIT PULL v3] STi SoC changes for v4.8
Date: Mon, 11 Jul 2016 09:41:17 +0200 [thread overview]
Message-ID: <57834D9D.4070900@st.com> (raw)
Hi Olof, Arnd and Kevin,
Please consider this first round of STi SoC updates for v4.8:
The following changes since commit 5edb56491d4812c42175980759da53388e5d86f5:
Linux 4.7-rc3 (2016-06-12 07:20:35 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/pchotard/sti.git
tags/sti-soc-for-v4.8
for you to fetch changes up to 7b8e0188fa717cd9abc4fb52587445b421835c2a:
ARM: sti: Implement dummy L2 cache's write_sec (2016-07-11 09:15:44
+0200)
----------------------------------------------------------------
Highlights:
-----------
- Add a dummy L2 cache's write_sec callback as in non secure mode execution,
we can't get access to L2 cache secure registers
- Cosmetics change, in case of dump_stack, update the hardware name with a
more generic for the STi SoCs family
----------------------------------------------------------------
Patrice Chotard (1):
ARM: sti: Implement dummy L2 cache's write_sec
Peter Griffin (1):
ARM: STi: Update machine _namestr to be more generic.
arch/arm/mach-sti/board-dt.c | 11 ++++++++++-
1 file changed, 10 insertions(+), 1 deletion(-)
next reply other threads:[~2016-07-11 7:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-11 7:41 Patrice Chotard [this message]
2016-07-11 7:41 ` [GIT PULL v3] STi SoC changes for v4.8 Patrice Chotard
2016-07-14 13:10 ` Arnd Bergmann
2016-07-14 13:10 ` 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=57834D9D.4070900@st.com \
--to=patrice.chotard@st.com \
--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.