[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2023100826-cranium-granite-be85@gregkh>
Date: Sun, 8 Oct 2023 15:07:45 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: "Peng Fan (OSS)" <peng.fan@....nxp.com>
Cc: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
Shawn Guo <shawnguo@...nel.org>,
Sascha Hauer <s.hauer@...gutronix.de>,
Pengutronix Kernel Team <kernel@...gutronix.de>,
Fabio Estevam <festevam@...il.com>,
NXP Linux Team <linux-imx@....com>,
Anson Huang <Anson.Huang@....com>, Bai Ping <ping.bai@....com>,
Stefan Wahren <stefan.wahren@...e.com>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
Peng Fan <peng.fan@....com>
Subject: Re: [PATCH 1/3] nvmem: imx: correct nregs for i.MX6SLL
On Sun, Oct 08, 2023 at 04:10:20PM +0800, Peng Fan (OSS) wrote:
> From: Peng Fan <peng.fan@....com>
>
> The nregs for i.MX6SLL should be 80 per fuse map, correct it.
>
> Fixes: 6da27821a6f5 ("nvmem: imx-ocotp: add support for imx6sll")
> Signed-off-by: Peng Fan <peng.fan@....com>
> ---
> drivers/nvmem/imx-ocotp.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/nvmem/imx-ocotp.c b/drivers/nvmem/imx-ocotp.c
> index 434f197e27bf..c59cfe13a5f8 100644
> --- a/drivers/nvmem/imx-ocotp.c
> +++ b/drivers/nvmem/imx-ocotp.c
> @@ -498,7 +498,7 @@ static const struct ocotp_params imx6sl_params = {
> };
>
> static const struct ocotp_params imx6sll_params = {
> - .nregs = 128,
> + .nregs = 80,
> .bank_address_words = 0,
> .set_timing = imx_ocotp_set_imx6_timing,
> .ctrl = IMX_OCOTP_BM_CTRL_DEFAULT,
>
> --
> 2.37.1
>
Hi,
This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him
a patch that has triggered this response. He used to manually respond
to these common problems, but in order to save his sanity (he kept
writing the same thing over and over, yet to different people), I was
created. Hopefully you will not take offence and will fix the problem
in your patch and resubmit it so that it can be accepted into the Linux
kernel tree.
You are receiving this message because of the following common error(s)
as indicated below:
- You have marked a patch with a "Fixes:" tag for a commit that is in an
older released kernel, yet you do not have a cc: stable line in the
signed-off-by area at all, which means that the patch will not be
applied to any older kernel releases. To properly fix this, please
follow the documented rules in the
Documentation/process/stable-kernel-rules.rst file for how to resolve
this.
If you wish to discuss this problem further, or you have questions about
how to resolve this issue, please feel free to respond to this email and
Greg will reply once he has dug out from the pending patches received
from other developers.
thanks,
greg k-h's patch email bot
Powered by blists - more mailing lists