mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Jad Keskes <inasj268@gmail.com>
Cc: Tony Luck <tony.luck@intel.com>,
	linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] edac: edac_device_sysfs: reject poll_msec value 0
Date: Thu, 9 Jul 2026 20:24:24 -0700	[thread overview]
Message-ID: <20260710032424.GIalBl6K0YJ2js1gHo@fat_crate.local> (raw)
In-Reply-To: <20260708141000.1764100-1-inasj268@gmail.com>

On Wed, Jul 08, 2026 at 03:09:59PM +0100, Jad Keskes wrote:
> Subject: Re: [PATCH 1/2] edac: edac_device_sysfs: reject poll_msec value 0

Do

$ git log -p drivers/edac/

to get an idea about the commit title and formatting the EDAC tree does. In
this case:

EDAC/device_sysfs: Reject poll_msec value 0

> The comment says it must be at least 1ms but there was never a check.
> Writing 0 sets the workqueue delay to 0 jiffies, which makes it spin.

You might run this through AI to get better/more informative formulations.

Some hints about a good commit message:

https://docs.kernel.org/process/submitting-patches.html

> Signed-off-by: Jad Keskes <inasj268@gmail.com>
> ---
>  drivers/edac/edac_device_sysfs.c | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/drivers/edac/edac_device_sysfs.c b/drivers/edac/edac_device_sysfs.c
> index da804ebe3626..3137cf6cf36b 100644
> --- a/drivers/edac/edac_device_sysfs.c
> +++ b/drivers/edac/edac_device_sysfs.c
> @@ -117,6 +117,10 @@ static ssize_t edac_device_ctl_poll_msec_store(struct edac_device_ctl_info
>  	ret = kstrtoul(data, 0, &value);

If you do those patches ontop of your previous ones, it doesn't apply:

checking file drivers/edac/edac_device_sysfs.c
Hunk #1 FAILED at 117.
1 out of 1 hunk FAILED

But you need to do those fixes first and then the conversion to kstrtoul()
because the fixes will go to stable while the kstrtoul() conversion is not
stable material.

Which means, you'd need to add a Fixes: tag to those but that's fine if you
can't find which patch causes this - I believe this has always been this way.

So, how about a new patchset with all that review feedback addressed, the
fixes first, the conversion following, all nicely tested, if you don't know
how use this here in a VM:

https://lore.kernel.org/all/20260707215307.396571-1-bp@kernel.org

Thanks.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

      parent reply	other threads:[~2026-07-10  3:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-08 14:09 Jad Keskes
2026-07-08 14:10 ` [PATCH 2/2] edac: edac_device: don't re-arm workqueue during teardown Jad Keskes
2026-07-10  3:24 ` Borislav Petkov [this message]

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=20260710032424.GIalBl6K0YJ2js1gHo@fat_crate.local \
    --to=bp@alien8.de \
    --cc=inasj268@gmail.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tony.luck@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

all inboxes | Powered by JetHome®