From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL v3] STi SoC changes for v4.8
Date: Thu, 14 Jul 2016 15:10:40 +0200 [thread overview]
Message-ID: <5162937.DKTOH8rVm0@wuerfel> (raw)
In-Reply-To: <57834D9D.4070900@st.com>
On Monday, July 11, 2016 9:41:17 AM CEST Patrice Chotard wrote:
> 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
Merged into next/soc. Note that you can skip the "Highlights" and "-------"
lines in the tag, just write it the way you want it to appear in the
git history. I actually prefer normal sentences, but lists like you have
here are also fine. Ideally start with a one-line description of
the branch.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Patrice Chotard <patrice.chotard@st.com>,
Olof Johansson <olof@lixom.net>,
Kevin Hilman <khilman@baylibre.com>,
arm@kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"open list:ARM/STI ARCHITECTURE" <kernel@stlinux.com>,
Peter Griffin <peter.griffin@linaro.org>
Subject: Re: [GIT PULL v3] STi SoC changes for v4.8
Date: Thu, 14 Jul 2016 15:10:40 +0200 [thread overview]
Message-ID: <5162937.DKTOH8rVm0@wuerfel> (raw)
In-Reply-To: <57834D9D.4070900@st.com>
On Monday, July 11, 2016 9:41:17 AM CEST Patrice Chotard wrote:
> 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
Merged into next/soc. Note that you can skip the "Highlights" and "-------"
lines in the tag, just write it the way you want it to appear in the
git history. I actually prefer normal sentences, but lists like you have
here are also fine. Ideally start with a one-line description of
the branch.
Arnd
next prev parent reply other threads:[~2016-07-14 13:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-11 7:41 [GIT PULL v3] STi SoC changes for v4.8 Patrice Chotard
2016-07-11 7:41 ` Patrice Chotard
2016-07-14 13:10 ` Arnd Bergmann [this message]
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=5162937.DKTOH8rVm0@wuerfel \
--to=arnd@arndb.de \
--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.