linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: patrice.chotard@st.com (Patrice Chotard)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] STi SoC changes for v4.8
Date: Thu, 7 Jul 2016 09:14:04 +0200	[thread overview]
Message-ID: <577E013C.7030208@st.com> (raw)
In-Reply-To: <20160707053056.GM32389@localhost>

Hi Olof

On 07/07/2016 07:30 AM, Olof Johansson wrote:
> On Fri, Jul 01, 2016 at 04:47:46PM +0200, 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
> Again, that's a branch and not a tag.

Right, i will fix that

>
>> 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
> Minor nit: This is a somewhat odd format to write a list in. Please use
> '-' or '*' instead, and feel free to use capital letters, etc. :)

Thanks for reviewing, i will submit a v2

Patrice
>
>
> -Olof

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-01 14:47 [GIT PULL] STi SoC changes for v4.8 Patrice Chotard
2016-07-07  5:30 ` Olof Johansson
2016-07-07  7:14   ` 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=577E013C.7030208@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 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).