All of lore.kernel.org
 help / color / mirror / Atom feed
From: khilman@baylibre.com (Kevin Hilman)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH v3 0/6] Add Amlogic secure monitor and NVMEM drivers
Date: Thu, 01 Sep 2016 14:27:01 -0700	[thread overview]
Message-ID: <m260qfia56.fsf@baylibre.com> (raw)
In-Reply-To: <20160827134757.GA4957@localhost> (Carlo Caione's message of "Sat, 27 Aug 2016 15:47:57 +0200")

Carlo Caione <carlo@caione.org> writes:

> On 27/08/16 15:43, Carlo Caione wrote:
>> From: Carlo Caione <carlo@endlessm.com>
>> 
>> I decided to respin again the secure monitor driver this time with the NVMEM
>> driver in the same patchset to have a clear view on how a generic driver can
>> use the monitor.
>
> Kevin,
> finally I found the time to respin this patchset for the last time.
> Since we have now all the ACKs we need, could you please take all the 6
> patches in your tree?

Patches 1, 4 applied to drivers branch.  The rest applied to dt64
branch.

Thanks,

Kevin

WARNING: multiple messages have this Message-ID (diff)
From: khilman@baylibre.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/6] Add Amlogic secure monitor and NVMEM drivers
Date: Thu, 01 Sep 2016 14:27:01 -0700	[thread overview]
Message-ID: <m260qfia56.fsf@baylibre.com> (raw)
In-Reply-To: <20160827134757.GA4957@localhost> (Carlo Caione's message of "Sat, 27 Aug 2016 15:47:57 +0200")

Carlo Caione <carlo@caione.org> writes:

> On 27/08/16 15:43, Carlo Caione wrote:
>> From: Carlo Caione <carlo@endlessm.com>
>> 
>> I decided to respin again the secure monitor driver this time with the NVMEM
>> driver in the same patchset to have a clear view on how a generic driver can
>> use the monitor.
>
> Kevin,
> finally I found the time to respin this patchset for the last time.
> Since we have now all the ACKs we need, could you please take all the 6
> patches in your tree?

Patches 1, 4 applied to drivers branch.  The rest applied to dt64
branch.

Thanks,

Kevin

  reply	other threads:[~2016-09-01 21:27 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-27 13:43 [PATCH v3 0/6] Add Amlogic secure monitor and NVMEM drivers Carlo Caione
2016-08-27 13:43 ` Carlo Caione
2016-08-27 13:43 ` [PATCH v3 1/6] firmware: Amlogic: Add secure monitor driver Carlo Caione
2016-08-27 13:43   ` Carlo Caione
2016-08-27 13:43 ` [PATCH v3 2/6] documentation: Add secure monitor bindings documentation Carlo Caione
2016-08-27 13:43   ` Carlo Caione
2016-08-27 13:43 ` [PATCH v3 3/6] ARM64: dts: amlogic: gxbb: Enable secure monitor Carlo Caione
2016-08-27 13:43   ` Carlo Caione
2016-08-27 13:43 ` [PATCH v3 4/6] nvmem: amlogic: Add Amlogic Meson EFUSE driver Carlo Caione
2016-08-27 13:43   ` Carlo Caione
2016-08-27 13:43 ` [PATCH v3 5/6] documentation: Add nvmem bindings documentation Carlo Caione
2016-08-27 13:43   ` Carlo Caione
2016-08-27 13:43 ` [PATCH v3 6/6] ARM64: dts: amlogic: gxbb: Enable NVMEM Carlo Caione
2016-08-27 13:43   ` Carlo Caione
2016-09-01 21:26   ` Kevin Hilman
2016-09-01 21:26     ` Kevin Hilman
2016-09-01 21:28     ` Carlo Caione
2016-09-01 21:28       ` Carlo Caione
2016-08-27 13:47 ` [PATCH v3 0/6] Add Amlogic secure monitor and NVMEM drivers Carlo Caione
2016-08-27 13:47   ` Carlo Caione
2016-09-01 21:27   ` Kevin Hilman [this message]
2016-09-01 21:27     ` Kevin Hilman

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=m260qfia56.fsf@baylibre.com \
    --to=khilman@baylibre.com \
    --cc=linus-amlogic@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.