From: Lee Jones <lee.jones@linaro.org>
To: Russ Weight <russell.h.weight@intel.com>
Cc: mdf@kernel.org, hao.wu@intel.com, yilun.xu@intel.com,
linux-fpga@vger.kernel.org, linux-kernel@vger.kernel.org,
trix@redhat.com, marpagan@redhat.com, lgoncalv@redhat.com,
matthew.gerlach@linux.intel.com,
basheer.ahmed.muddebihal@intel.com, tianfei.zhang@intel.com
Subject: Re: [PATCH v23 1/5] mfd: intel-m10-bmc: Rename n3000bmc-secure driver
Date: Wed, 8 Jun 2022 08:46:28 +0100 [thread overview]
Message-ID: <YqBT1O9dxAqeFphE@google.com> (raw)
In-Reply-To: <20220606160038.846236-2-russell.h.weight@intel.com>
On Mon, 06 Jun 2022, Russ Weight wrote:
> The n3000bmc-secure driver has changed to n3000bmc-sec-update. Update
> the name in the list of the intel-m10-bmc sub-drivers.
>
> Tested-by: Tianfei Zhang <tianfei.zhang@intel.com>
> Acked-by: Xu Yilun <yilun.xu@intel.com>
> Signed-off-by: Russ Weight <russell.h.weight@intel.com>
> ---
> v23:
> - Rebased for 5.19-rc1
> v22:
> - Added Tested-by tag from Tianfei and Acked-by tag from Yilun.
> v21:
> - No change
> v20:
> - No change
> v19:
> - No change
> v18:
> - No change
> v17:
> - This is a new patch to change in the name of the secure update
> driver.
> ---
> drivers/mfd/intel-m10-bmc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Acked-by: Lee Jones <lee.jones@linaro.org>
--
Lee Jones [李琼斯]
Principal Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2022-06-08 8:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 16:00 [PATCH v23 0/5] FPGA MAX10 BMC Secure Update Driver Russ Weight
2022-06-06 16:00 ` [PATCH v23 1/5] mfd: intel-m10-bmc: Rename n3000bmc-secure driver Russ Weight
2022-06-08 7:46 ` Lee Jones [this message]
2022-06-08 9:26 ` Xu Yilun
2022-06-06 16:00 ` [PATCH v23 2/5] fpga: m10bmc-sec: create max10 bmc secure update Russ Weight
2022-06-06 16:00 ` [PATCH v23 3/5] fpga: m10bmc-sec: expose max10 flash update count Russ Weight
2022-06-06 16:00 ` [PATCH v23 4/5] fpga: m10bmc-sec: expose max10 canceled keys in sysfs Russ Weight
2022-06-06 16:00 ` [PATCH v23 5/5] fpga: m10bmc-sec: add max10 secure update functions Russ Weight
2022-06-07 14:53 ` [PATCH v23 0/5] FPGA MAX10 BMC Secure Update Driver Xu Yilun
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=YqBT1O9dxAqeFphE@google.com \
--to=lee.jones@linaro.org \
--cc=basheer.ahmed.muddebihal@intel.com \
--cc=hao.wu@intel.com \
--cc=lgoncalv@redhat.com \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marpagan@redhat.com \
--cc=matthew.gerlach@linux.intel.com \
--cc=mdf@kernel.org \
--cc=russell.h.weight@intel.com \
--cc=tianfei.zhang@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;
as well as URLs for NNTP newsgroup(s).