[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Yx2QwSG52+Iq8Ysa@yilunxu-OptiPlex-7050>
Date: Sun, 11 Sep 2022 15:39:45 +0800
From: Xu Yilun <yilun.xu@...el.com>
To: Russ Weight <russell.h.weight@...el.com>
Cc: mdf@...nel.org, hao.wu@...el.com, trix@...hat.com, lee@...nel.org,
linux-fpga@...r.kernel.org, linux-kernel@...r.kernel.org,
lgoncalv@...hat.com, marpagan@...hat.com,
matthew.gerlach@...ux.intel.com,
basheer.ahmed.muddebihal@...el.com, tianfei.zhang@...el.com
Subject: Re: [PATCH v1 2/2] fpga: m10bmc-sec: d5005 bmc secure update driver
On 2022-09-02 at 09:57:06 -0700, Russ Weight wrote:
> Add a driver name for the D5005 BMC secure update driver. Different
> driver names are used for the N3000 and D5005 devices because future
> changes will add conditional code based on the device type (N3000
> vs D5005). This change enables D5005 secure updates of BCM images,
> BMC firmware, static-region images, etc.
>
> Signed-off-by: Russ Weight <russell.h.weight@...el.com>
> ---
> drivers/fpga/intel-m10-bmc-sec-update.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/fpga/intel-m10-bmc-sec-update.c b/drivers/fpga/intel-m10-bmc-sec-update.c
> index 72c677c910de..526c8cdd1474 100644
> --- a/drivers/fpga/intel-m10-bmc-sec-update.c
> +++ b/drivers/fpga/intel-m10-bmc-sec-update.c
> @@ -605,6 +605,9 @@ static const struct platform_device_id intel_m10bmc_sec_ids[] = {
> {
> .name = "n3000bmc-sec-update",
> },
> + {
> + .name = "d5005bmc-sec-update",
> + },
> { }
> };
> MODULE_DEVICE_TABLE(platform, intel_m10bmc_sec_ids);
Applied to for-next.
Thanks,
Yilun
> --
> 2.25.1
>
Powered by blists - more mailing lists