All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: [PATCHv5 0/6] SCP03 control, documentation and tests.
Date: Thu, 11 Mar 2021 21:45:48 -0700	[thread overview]
Message-ID: <CAPnjgZ2Rz=4grZ2c-MQpSynoHUkZ6+KRixs543QWC43rFSHXOA@mail.gmail.com> (raw)
In-Reply-To: <20210310165931.GA32762@trex>

Hi Foundries,

On Wed, 10 Mar 2021 at 09:59, Jorge Ramirez-Ortiz, Foundries
<jorge@foundries.io> wrote:
>
> On 14/02/21, Jorge Ramirez-Ortiz wrote:
> > Simply adding the reviewed-by tags to the v5 series.
>
> why has this not been merged yet?

You can check in patchwork to see whose queue it is in.

Regards,
Simon

  reply	other threads:[~2021-03-12  4:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-14 15:27 [PATCHv5 0/6] SCP03 control, documentation and tests Jorge Ramirez-Ortiz
2021-02-14 15:27 ` [PATCHv5 1/6] common: SCP03 control (enable and provision of keys) Jorge Ramirez-Ortiz
2021-03-15 15:52   ` Tom Rini
2021-02-14 15:27 ` [PATCHv5 2/6] cmd: SCP03: enable and provision command Jorge Ramirez-Ortiz
2021-02-15 13:14   ` Igor Opaniuk
2021-03-15 15:52   ` Tom Rini
2021-02-14 15:27 ` [PATCHv5 3/6] drivers: tee: sandbox: SCP03 control emulator Jorge Ramirez-Ortiz
2021-03-15 15:53   ` Tom Rini
2021-02-14 15:27 ` [PATCHv5 4/6] doc: describe the scp03 command Jorge Ramirez-Ortiz
2021-03-15 15:53   ` Tom Rini
2021-02-14 15:27 ` [PATCHv5 5/6] sandbox: imply SCP03 and CMD_SCP03 Jorge Ramirez-Ortiz
2021-03-15 15:53   ` Tom Rini
2021-02-14 15:27 ` [PATCHv5 6/6] test: py: add initial coverage for scp03 cmd Jorge Ramirez-Ortiz
2021-03-15 15:53   ` Tom Rini
2021-03-10 16:59 ` [PATCHv5 0/6] SCP03 control, documentation and tests Jorge
2021-03-12  4:45   ` Simon Glass [this message]
2021-03-12  8:28     ` Jorge
2021-03-12 13:26       ` Tom Rini
2021-03-12 13:31         ` Jorge

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='CAPnjgZ2Rz=4grZ2c-MQpSynoHUkZ6+KRixs543QWC43rFSHXOA@mail.gmail.com' \
    --to=sjg@chromium.org \
    --cc=u-boot@lists.denx.de \
    /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.