mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Russ Weight <russell.h.weight@intel.com>
To: lee.jones@linaro.org, linux-kernel@vger.kernel.org
Cc: trix@redhat.com, lgoncalv@redhat.com, yilun.xu@intel.com,
	hao.wu@intel.com, matthew.gerlach@intel.com
Subject: Re: [PATCH v8 0/1] Intel MAX10 BMC Macros for Secure Update
Date: Thu, 21 Jan 2021 15:56:15 -0800	[thread overview]
Message-ID: <6be5e8f1-d6c5-cdc8-4342-7dfa60bbed4f@intel.com> (raw)
In-Reply-To: <20210121225555.302548-1-russell.h.weight@intel.com>



On 1/21/21 2:55 PM, Russ Weight wrote:
> This patch was previously patch 1 of 6 in the patch-series entitled
> "Intel MAX10 BMC Secure Update Driver". This is the only patch in
> the series that is subject to conflicts with other ongoing changes
> and is separated here to simplify maintenance of the patchset.
>
> This patch creates a number of macro definitions that are required
> for the Intel MAX10 BMC Secure Update Driver.

Please apply this patch first. It was previously accepted but has not
landed in linux-next yet.
https://marc.info/?l=linux-kernel&m=161066634118704&w=2
>
> Changelog v7 -> v8:
>   - Rebased on next-20210121
>   - Separated out from patchset: "Intel MAX10 BMC Secure Update Driver"
> Changelog v6 -> v7:
>   - No change
> Changelog v5 -> v6:
>   - No change
> Changelog v4 -> v5:
>   - Renamed USER_FLASH_COUNT to STAGING_FLASH_COUNT
> Changelog v3 -> v4:
>   - No change
> Changelog v2 -> v3:
>   - Changed "MAX10 BMC Secure Engine driver" to "MAX10 BMC Secure
>     Update driver"
>   - Removed wrapper functions (m10bmc_raw_*, m10bmc_sys_*). The
>     underlying functions will be called directly.
> Changelog v1 -> v2:
>   - These functions and macros were previously distributed among
>     the patches that needed them. They are now grouped together
>     in a single patch containing changes to the Intel MAX10 BMC
>     driver.
>   - Added DRBL_ prefix to some definitions
>   - Some address definitions were moved here from the .c files that
>     use them.
>
> Russ Weight (1):
>   mfd: intel-m10-bmc: support for MAX10 BMC Secure Updates
>
>  include/linux/mfd/intel-m10-bmc.h | 85 +++++++++++++++++++++++++++++++
>  1 file changed, 85 insertions(+)
>


  parent reply	other threads:[~2021-01-21 23:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-21 22:55 Russ Weight
2021-01-21 22:55 ` [PATCH v8 1/1] mfd: intel-m10-bmc: support for MAX10 BMC Secure Updates Russ Weight
2021-01-21 23:56 ` Russ Weight [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-01-21 22:54 [PATCH v8 0/1] Intel MAX10 BMC Macros for Secure Update Russ Weight

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=6be5e8f1-d6c5-cdc8-4342-7dfa60bbed4f@intel.com \
    --to=russell.h.weight@intel.com \
    --cc=hao.wu@intel.com \
    --cc=lee.jones@linaro.org \
    --cc=lgoncalv@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew.gerlach@intel.com \
    --cc=trix@redhat.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

all inboxes | Powered by JetHome®