From: Xu Yilun <yilun.xu@linux.intel.com>
To: "Colberg, Peter" <peter.colberg@intel.com>
Cc: "russ.weight@linux.dev" <russ.weight@linux.dev>,
"Wu, Hao" <hao.wu@intel.com>, "mdf@kernel.org" <mdf@kernel.org>,
"linux-fpga@vger.kernel.org" <linux-fpga@vger.kernel.org>,
"Xu, Yilun" <yilun.xu@intel.com>, "Rix, Tom" <trix@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"matthew.gerlach@linux.intel.com"
<matthew.gerlach@linux.intel.com>
Subject: Re: [PATCH 2/3] fpga: m10bmc-sec: Change contact for secure update driver
Date: Sat, 7 Oct 2023 14:52:46 +0800 [thread overview]
Message-ID: <ZSEAPvn6FS2Rcesq@yilunxu-OptiPlex-7050> (raw)
In-Reply-To: <7e67b2684e5b58bd61fcc7110ca90e1387f5e0ea.camel@intel.com>
On Wed, Oct 04, 2023 at 11:19:30PM +0000, Colberg, Peter wrote:
> On Thu, 2023-09-28 at 09:47 -0700, Russ Weight wrote:
> > Change the maintainer for the Intel MAX10 BMC Secure Update driver from
> > Russ Weight to Peter Colberg. Update the ABI documentation contact
> > information as well.
> >
> > Signed-off-by: Russ Weight <russell.h.weight@intel.com>
>
> Acked-by: Peter Colberg <peter.colberg@intel.com>
Applied.
Thanks,
Yilun
>
> > ---
> > .../testing/sysfs-driver-intel-m10-bmc-sec-update | 14 +++++++-------
> > MAINTAINERS | 2 +-
> > 2 files changed, 8 insertions(+), 8 deletions(-)
> >
> > diff --git a/Documentation/ABI/testing/sysfs-driver-intel-m10-bmc-sec-update b/Documentation/ABI/testing/sysfs-driver-intel-m10-bmc-sec-update
> > index 0a41afe0ab4c..9051695d2211 100644
> > --- a/Documentation/ABI/testing/sysfs-driver-intel-m10-bmc-sec-update
> > +++ b/Documentation/ABI/testing/sysfs-driver-intel-m10-bmc-sec-update
> > @@ -1,7 +1,7 @@
> > What: /sys/bus/platform/drivers/intel-m10bmc-sec-update/.../security/sr_root_entry_hash
> > Date: Sep 2022
> > KernelVersion: 5.20
> > -Contact: Russ Weight <russell.h.weight@intel.com>
> > +Contact: Peter Colberg <peter.colberg@intel.com>
> > Description: Read only. Returns the root entry hash for the static
> > region if one is programmed, else it returns the
> > string: "hash not programmed". This file is only
> > @@ -11,7 +11,7 @@ Description: Read only. Returns the root entry hash for the static
> > What: /sys/bus/platform/drivers/intel-m10bmc-sec-update/.../security/pr_root_entry_hash
> > Date: Sep 2022
> > KernelVersion: 5.20
> > -Contact: Russ Weight <russell.h.weight@intel.com>
> > +Contact: Peter Colberg <peter.colberg@intel.com>
> > Description: Read only. Returns the root entry hash for the partial
> > reconfiguration region if one is programmed, else it
> > returns the string: "hash not programmed". This file
> > @@ -21,7 +21,7 @@ Description: Read only. Returns the root entry hash for the partial
> > What: /sys/bus/platform/drivers/intel-m10bmc-sec-update/.../security/bmc_root_entry_hash
> > Date: Sep 2022
> > KernelVersion: 5.20
> > -Contact: Russ Weight <russell.h.weight@intel.com>
> > +Contact: Peter Colberg <peter.colberg@intel.com>
> > Description: Read only. Returns the root entry hash for the BMC image
> > if one is programmed, else it returns the string:
> > "hash not programmed". This file is only visible if the
> > @@ -31,7 +31,7 @@ Description: Read only. Returns the root entry hash for the BMC image
> > What: /sys/bus/platform/drivers/intel-m10bmc-sec-update/.../security/sr_canceled_csks
> > Date: Sep 2022
> > KernelVersion: 5.20
> > -Contact: Russ Weight <russell.h.weight@intel.com>
> > +Contact: Peter Colberg <peter.colberg@intel.com>
> > Description: Read only. Returns a list of indices for canceled code
> > signing keys for the static region. The standard bitmap
> > list format is used (e.g. "1,2-6,9").
> > @@ -39,7 +39,7 @@ Description: Read only. Returns a list of indices for canceled code
> > What: /sys/bus/platform/drivers/intel-m10bmc-sec-update/.../security/pr_canceled_csks
> > Date: Sep 2022
> > KernelVersion: 5.20
> > -Contact: Russ Weight <russell.h.weight@intel.com>
> > +Contact: Peter Colberg <peter.colberg@intel.com>
> > Description: Read only. Returns a list of indices for canceled code
> > signing keys for the partial reconfiguration region. The
> > standard bitmap list format is used (e.g. "1,2-6,9").
> > @@ -47,7 +47,7 @@ Description: Read only. Returns a list of indices for canceled code
> > What: /sys/bus/platform/drivers/intel-m10bmc-sec-update/.../security/bmc_canceled_csks
> > Date: Sep 2022
> > KernelVersion: 5.20
> > -Contact: Russ Weight <russell.h.weight@intel.com>
> > +Contact: Peter Colberg <peter.colberg@intel.com>
> > Description: Read only. Returns a list of indices for canceled code
> > signing keys for the BMC. The standard bitmap list format
> > is used (e.g. "1,2-6,9").
> > @@ -55,7 +55,7 @@ Description: Read only. Returns a list of indices for canceled code
> > What: /sys/bus/platform/drivers/intel-m10bmc-sec-update/.../security/flash_count
> > Date: Sep 2022
> > KernelVersion: 5.20
> > -Contact: Russ Weight <russell.h.weight@intel.com>
> > +Contact: Peter Colberg <peter.colberg@intel.com>
> > Description: Read only. Returns number of times the secure update
> > staging area has been flashed.
> > Format: "%u".
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index b97ee6f50679..8006c35956bb 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -10755,7 +10755,7 @@ F: drivers/mfd/intel-m10-bmc*
> > F: include/linux/mfd/intel-m10-bmc.h
> >
> > INTEL MAX10 BMC SECURE UPDATES
> > -M: Russ Weight <russell.h.weight@intel.com>
> > +M: Peter Colberg <peter.colberg@intel.com>
> > L: linux-fpga@vger.kernel.org
> > S: Maintained
> > F: Documentation/ABI/testing/sysfs-driver-intel-m10-bmc-sec-update
>
prev parent reply other threads:[~2023-10-07 6:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 16:47 [PATCH 2/3] fpga: m10bmc-sec: Change contact for secure update driver Russ Weight
2023-09-29 15:04 ` Xu Yilun
2023-10-04 23:19 ` Colberg, Peter
2023-10-07 6:52 ` Xu Yilun [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=ZSEAPvn6FS2Rcesq@yilunxu-OptiPlex-7050 \
--to=yilun.xu@linux.intel.com \
--cc=hao.wu@intel.com \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.gerlach@linux.intel.com \
--cc=mdf@kernel.org \
--cc=peter.colberg@intel.com \
--cc=russ.weight@linux.dev \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).