[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <YoSyRQbX/oH3UhFw@kroah.com>
Date: Wed, 18 May 2022 10:45:57 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Yang Yingliang <yangyingliang@...wei.com>
Cc: linux-kernel@...r.kernel.org, linux-hwmon@...r.kernel.org,
zbr@...emap.net, jdelvare@...e.com, linux@...ck-us.net
Subject: Re: [PATCH -next] drivers: w1: drop unnecessary memset() in
w1_master_release()
On Wed, May 18, 2022 at 04:01:36PM +0800, Yang Yingliang wrote:
> It's unnecessary to use memset() in w1_master_release() before
> the memory is freed, so remove it.
>
> Signed-off-by: Yang Yingliang <yangyingliang@...wei.com>
> ---
> drivers/w1/w1.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/w1/w1.c b/drivers/w1/w1.c
> index f2ae2e563dc5..f4d1499bb853 100644
> --- a/drivers/w1/w1.c
> +++ b/drivers/w1/w1.c
> @@ -73,7 +73,6 @@ static void w1_master_release(struct device *dev)
> struct w1_master *md = dev_to_w1_master(dev);
>
> dev_dbg(dev, "%s: Releasing %s.\n", __func__, md->name);
> - memset(md, 0, sizeof(struct w1_master) + sizeof(struct w1_bus_master));
> kfree(md);
> }
>
> --
> 2.25.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:
- This looks like a new version of a previously submitted patch, but you
did not list below the --- line any changes from the previous version.
Please read the section entitled "The canonical patch format" in the
kernel file, Documentation/SubmittingPatches for what needs to be done
here to properly describe 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