public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Patrice Chotard <patrice.chotard@st.com>
To: Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
	Kevin Hilman <khilman@baylibre.com>, <arm@kernel.org>
Cc: Peter Griffin <peter.griffin@linaro.org>,
	Lee Jones <lee.jones@linaro.org>,
	"open list:ARM/STI ARCHITECTURE" <kernel@stlinux.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: STi SoC changes for v4.8
Date: Fri, 1 Jul 2016 16:46:26 +0200	[thread overview]
Message-ID: <57768242.6090007@st.com> (raw)
In-Reply-To: <57767EDE.8050708@st.com>

Sorry, i resend with the correct subject including [GIT PULL] prefix

On 07/01/2016 04:31 PM, Patrice Chotard wrote:
> Hi Olof, Arnd and Kevin,
>
> Please consider this first round of STi SoC updates for v4.8:
>
> The following changes since commit 
> 4c2e07c6a29e0129e975727b9f57eede813eea85:
>
>   Linux 4.7-rc5 (2016-06-26 17:52:03 -0700)
>
> are available in the git repository at:
>
>   git://git.kernel.org/pub/scm/linux/kernel/git/pchotard/sti.git 
> sti-soc_for_v4.8
>
> for you to fetch changes up to 55aa35180c57d82f3db23e5aabce97acb0d36681:
>
>   ARM: sti: Implement dummy L2 cache's write_sec (2016-07-01 16:23: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 genericfor 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(-)
>

      reply	other threads:[~2016-07-01 14:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-01 14:31 STi SoC changes for v4.8 Patrice Chotard
2016-07-01 14:46 ` Patrice Chotard [this message]

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=57768242.6090007@st.com \
    --to=patrice.chotard@st.com \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=kernel@stlinux.com \
    --cc=khilman@baylibre.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=peter.griffin@linaro.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