linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Xu Yilun <yilun.xu@intel.com>
To: Russ Weight <russell.h.weight@intel.com>
Cc: mdf@kernel.org, hao.wu@intel.com, lee.jones@linaro.org,
	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 v21 1/5] mfd: intel-m10-bmc: Rename n3000bmc-secure driver
Date: Thu, 26 May 2022 15:54:13 +0800	[thread overview]
Message-ID: <20220526075413.GB148394@yilunxu-OptiPlex-7050> (raw)
In-Reply-To: <20220521003607.737734-2-russell.h.weight@intel.com>

On Fri, May 20, 2022 at 05:36:03PM -0700, 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.
> 
> Signed-off-by: Russ Weight <russell.h.weight@intel.com>
> ---
> 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(-)
> 
> 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" },

Acked-by: Xu Yilun <yilun.xu@intel.com>

Hi Lee:

Is it good to you? If yes, could I apply this patch to linux-fpga
and submit along with the other patches in this series?

Thanks,
Yilun

>  };
>  
>  static struct mfd_cell m10bmc_n5010_subdevs[] = {
> -- 
> 2.25.1

  reply	other threads:[~2022-05-26  8:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-21  0:36 [PATCH v21 0/5] FPGA MAX10 BMC Secure Update Driver Russ Weight
2022-05-21  0:36 ` [PATCH v21 1/5] mfd: intel-m10-bmc: Rename n3000bmc-secure driver Russ Weight
2022-05-26  7:54   ` Xu Yilun [this message]
2022-05-26  8:31     ` Lee Jones
2022-05-21  0:36 ` [PATCH v21 2/5] fpga: m10bmc-sec: create max10 bmc secure update Russ Weight
2022-05-26  7:55   ` Xu Yilun
2022-05-26  8:04   ` Xu Yilun
2022-05-26 20:48     ` Russ Weight
2022-05-21  0:36 ` [PATCH v21 3/5] fpga: m10bmc-sec: expose max10 flash update count Russ Weight
2022-05-26  7:55   ` Xu Yilun
2022-05-21  0:36 ` [PATCH v21 4/5] fpga: m10bmc-sec: expose max10 canceled keys in sysfs Russ Weight
2022-05-26  7:56   ` Xu Yilun
2022-05-21  0:36 ` [PATCH v21 5/5] fpga: m10bmc-sec: add max10 secure update functions Russ Weight
2022-05-26  7:48   ` Xu Yilun
2022-05-26 21:27     ` Russ Weight
2022-05-27  4:47       ` Xu Yilun
2022-05-27 19:26         ` 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=20220526075413.GB148394@yilunxu-OptiPlex-7050 \
    --to=yilun.xu@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=russell.h.weight@intel.com \
    --cc=tianfei.zhang@intel.com \
    --cc=trix@redhat.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).