linux-fpga.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tom Rix <trix@redhat.com>
To: Russ Weight <russell.h.weight@intel.com>,
	mdf@kernel.org, linux-fpga@vger.kernel.org,
	linux-kernel@vger.kernel.org, "Wu, Hao" <hao.wu@intel.com>
Cc: lgoncalv@redhat.com, yilun.xu@intel.com,
	matthew.gerlach@intel.com, richard.gong@intel.com
Subject: Re: [PATCH v13 0/4] Intel MAX10 BMC Secure Update Driver
Date: Wed, 28 Jul 2021 07:56:16 -0700	[thread overview]
Message-ID: <65ed311d-a492-413e-33a8-f64e9c41e7c2@redhat.com> (raw)
In-Reply-To: <20210727225859.153572-1-russell.h.weight@intel.com>

Russ
> Russ Weight (4):
>    fpga: m10bmc-sec: create max10 bmc secure update driver
>    fpga: m10bmc-sec: expose max10 flash update count
>    fpga: m10bmc-sec: expose max10 canceled keys in sysfs

Since sec-mgr is taking a long time, I am looking at splitting out parts 
we can agree on.

These 3 patches are a new dfl specific driver and do not depend on sec-mgr.

Here is a poc on char-misc-next, splitting them and moving them before 
sec-mgr

https://github.com/trixirt/linux-next/commits/sec-mgr-reorder

Moritz, Hao

Could these 3 patches go into fpga-next now ?

Tom


>    fpga: m10bmc-sec: add max10 secure update functions


      parent reply	other threads:[~2021-07-28 14:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-27 22:58 [PATCH v13 0/4] Intel MAX10 BMC Secure Update Driver Russ Weight
2021-07-27 22:58 ` [PATCH v13 1/4] fpga: m10bmc-sec: create max10 bmc secure update driver Russ Weight
2021-07-27 22:58 ` [PATCH v13 2/4] fpga: m10bmc-sec: expose max10 flash update count Russ Weight
2021-07-27 22:58 ` [PATCH v13 3/4] fpga: m10bmc-sec: expose max10 canceled keys in sysfs Russ Weight
2021-07-27 22:58 ` [PATCH v13 4/4] fpga: m10bmc-sec: add max10 secure update functions Russ Weight
2021-07-28 14:56 ` Tom Rix [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=65ed311d-a492-413e-33a8-f64e9c41e7c2@redhat.com \
    --to=trix@redhat.com \
    --cc=hao.wu@intel.com \
    --cc=lgoncalv@redhat.com \
    --cc=linux-fpga@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew.gerlach@intel.com \
    --cc=mdf@kernel.org \
    --cc=richard.gong@intel.com \
    --cc=russell.h.weight@intel.com \
    --cc=yilun.xu@intel.com \
    /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).