linux-amlogic.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: carlo@caione.org (Carlo Caione)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH v3 0/6] Add Amlogic secure monitor and NVMEM drivers
Date: Sat, 27 Aug 2016 15:47:57 +0200	[thread overview]
Message-ID: <20160827134757.GA4957@localhost> (raw)
In-Reply-To: <1472305428-16874-1-git-send-email-carlo@caione.org>

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?

Thanks,

-- 
Carlo Caione

  parent reply	other threads:[~2016-08-27 13:47 UTC|newest]

Thread overview: 11+ 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 ` [PATCH v3 1/6] firmware: Amlogic: Add secure monitor driver Carlo Caione
2016-08-27 13:43 ` [PATCH v3 2/6] documentation: Add secure monitor bindings documentation 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 ` [PATCH v3 4/6] nvmem: amlogic: Add Amlogic Meson EFUSE driver Carlo Caione
2016-08-27 13:43 ` [PATCH v3 5/6] documentation: Add nvmem bindings documentation Carlo Caione
2016-08-27 13:43 ` [PATCH v3 6/6] ARM64: dts: amlogic: gxbb: Enable NVMEM Carlo Caione
2016-09-01 21:26   ` Kevin Hilman
2016-09-01 21:28     ` Carlo Caione
2016-08-27 13:47 ` Carlo Caione [this message]
2016-09-01 21:27   ` [PATCH v3 0/6] Add Amlogic secure monitor and NVMEM drivers 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=20160827134757.GA4957@localhost \
    --to=carlo@caione.org \
    --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 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).