From: Russ Weight <russell.h.weight@intel.com>
To: mdf@kernel.org, hao.wu@intel.com, yilun.xu@intel.com,
lee.jones@linaro.org, linux-fpga@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: trix@redhat.com, marpagan@redhat.com, lgoncalv@redhat.com,
matthew.gerlach@linux.intel.com,
basheer.ahmed.muddebihal@intel.com, tianfei.zhang@intel.com,
Russ Weight <russell.h.weight@intel.com>
Subject: [PATCH v19 1/5] mfd: intel-m10-bmc: Rename n3000bmc-secure driver
Date: Tue, 10 May 2022 12:56:31 -0700 [thread overview]
Message-ID: <20220510195635.140722-2-russell.h.weight@intel.com> (raw)
In-Reply-To: <20220510195635.140722-1-russell.h.weight@intel.com>
The n3000bmc-secure driver has changed to n3000bmc-sec-update. Update
the name in the list of the intel-m10-bmc sub-drivers.
Signed-off-by: Russ Weight <russell.h.weight@intel.com>
---
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(-)
diff --git a/drivers/mfd/intel-m10-bmc.c b/drivers/mfd/intel-m10-bmc.c
index 8db3bcf5fccc..f4d0d72573c8 100644
--- a/drivers/mfd/intel-m10-bmc.c
+++ b/drivers/mfd/intel-m10-bmc.c
@@ -26,7 +26,7 @@ static struct mfd_cell m10bmc_d5005_subdevs[] = {
static struct mfd_cell m10bmc_pacn3000_subdevs[] = {
{ .name = "n3000bmc-hwmon" },
{ .name = "n3000bmc-retimer" },
- { .name = "n3000bmc-secure" },
+ { .name = "n3000bmc-sec-update" },
};
static struct mfd_cell m10bmc_n5010_subdevs[] = {
--
2.25.1
next prev parent reply other threads:[~2022-05-10 19:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 19:56 [PATCH v19 0/5] FPGA MAX10 BMC Secure Update Driver Russ Weight
2022-05-10 19:56 ` Russ Weight [this message]
2022-05-10 19:56 ` [PATCH v19 2/5] fpga: m10bmc-sec: create max10 bmc secure update Russ Weight
2022-05-16 16:19 ` Xu Yilun
2022-05-16 20:44 ` Russ Weight
2022-05-10 19:56 ` [PATCH v19 3/5] fpga: m10bmc-sec: expose max10 flash update count Russ Weight
2022-05-10 19:56 ` [PATCH v19 4/5] fpga: m10bmc-sec: expose max10 canceled keys in sysfs Russ Weight
2022-05-10 19:56 ` [PATCH v19 5/5] fpga: m10bmc-sec: add max10 secure update functions 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=20220510195635.140722-2-russell.h.weight@intel.com \
--to=russell.h.weight@intel.com \
--cc=basheer.ahmed.muddebihal@intel.com \
--cc=hao.wu@intel.com \
--cc=lee.jones@linaro.org \
--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=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).