From: "Winiarska, Iwona" <iwona.winiarska@intel.com>
To: "linux@roeck-us.net" <linux@roeck-us.net>,
"christophe.jaillet@wanadoo.fr" <christophe.jaillet@wanadoo.fr>,
"jdelvare@suse.com" <jdelvare@suse.com>
Cc: "linux-hwmon@vger.kernel.org" <linux-hwmon@vger.kernel.org>,
"kernel-janitors@vger.kernel.org"
<kernel-janitors@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] hwmon: peci: Use devm_delayed_work_autocancel() to simplify code
Date: Mon, 14 Feb 2022 14:29:19 +0000 [thread overview]
Message-ID: <1696edf17cbab06c7e0ef453cd7bc3bed3ae9299.camel@intel.com> (raw)
In-Reply-To: <fd277a708ede3882d7df6831f02d2e3c0cb813b8.1644781718.git.christophe.jaillet@wanadoo.fr>
On Sun, 2022-02-13 at 20:48 +0100, Christophe JAILLET wrote:
> Use devm_delayed_work_autocancel() instead of hand writing it. This is
> less verbose and saves a few lines of code.
>
> devm_delayed_work_autocancel() uses devm_add_action() instead of
> devm_add_action_or_reset(). This is fine, because if the underlying memory
> allocation fails, no work has been scheduled yet. So there is nothing to
> undo.
>
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Reviewed-by: Iwona Winiarska <iwona.winiarska@intel.com>
Thanks
-Iwona
> ---
> drivers/hwmon/peci/dimmtemp.c | 13 +++----------
> 1 file changed, 3 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/hwmon/peci/dimmtemp.c b/drivers/hwmon/peci/dimmtemp.c
> index c8222354c005..96b9919db357 100644
> --- a/drivers/hwmon/peci/dimmtemp.c
> +++ b/drivers/hwmon/peci/dimmtemp.c
> @@ -4,6 +4,7 @@
> #include <linux/auxiliary_bus.h>
> #include <linux/bitfield.h>
> #include <linux/bitops.h>
> +#include <linux/devm-helpers.h>
> #include <linux/hwmon.h>
> #include <linux/jiffies.h>
> #include <linux/module.h>
> @@ -378,13 +379,6 @@ static void create_dimm_temp_info_delayed(struct
> work_struct *work)
> dev_err(priv->dev, "Failed to populate DIMM temp info\n");
> }
>
> -static void remove_delayed_work(void *_priv)
> -{
> - struct peci_dimmtemp *priv = _priv;
> -
> - cancel_delayed_work_sync(&priv->detect_work);
> -}
> -
> static int peci_dimmtemp_probe(struct auxiliary_device *adev, const struct
> auxiliary_device_id *id)
> {
> struct device *dev = &adev->dev;
> @@ -415,9 +409,8 @@ static int peci_dimmtemp_probe(struct auxiliary_device
> *adev, const struct auxil
> "Unexpected PECI revision %#x, some features may be
> unavailable\n",
> peci_dev->info.peci_revision);
>
> - INIT_DELAYED_WORK(&priv->detect_work, create_dimm_temp_info_delayed);
> -
> - ret = devm_add_action_or_reset(priv->dev, remove_delayed_work, priv);
> + ret = devm_delayed_work_autocancel(priv->dev, &priv->detect_work,
> + create_dimm_temp_info_delayed);
> if (ret)
> return ret;
>
next prev parent reply other threads:[~2022-02-14 14:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-13 19:48 Christophe JAILLET
2022-02-14 14:29 ` Winiarska, Iwona [this message]
2022-04-03 21:46 ` Guenter Roeck
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=1696edf17cbab06c7e0ef453cd7bc3bed3ae9299.camel@intel.com \
--to=iwona.winiarska@intel.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=jdelvare@suse.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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®