Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Vasileios Amoiridis <vassilisamir@gmail.com>
Cc: lars@metafoo.de, andriy.shevchenko@linux.intel.com,
	ang.iglesiasg@gmail.com, mazziesaccount@gmail.com,
	ak@it-klinger.de, petre.rodan@subdimension.ro,
	phil@raspberrypi.com, 579lpy@gmail.com, linus.walleij@linaro.org,
	semen.protsenko@linaro.org, linux-iio@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Jonathan Cameron <Jonathan.Cameron@huawei.com>
Subject: Re: [PATCH v7 2/5] iio: pressure: bmp280: Introduce new cleanup routines
Date: Sun, 19 May 2024 15:24:51 +0100	[thread overview]
Message-ID: <20240519152451.4e2782f5@jic23-huawei> (raw)
In-Reply-To: <20240512230524.53990-3-vassilisamir@gmail.com>

On Mon, 13 May 2024 01:05:21 +0200
Vasileios Amoiridis <vassilisamir@gmail.com> wrote:

> Introduce new linux/cleanup.h with the guard(mutex) functionality.
> 
> Suggested-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> Suggested-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> Signed-off-by: Vasileios Amoiridis <vassilisamir@gmail.com>

I put back the line accidentally deleted in this one whilst applying.

Jonathan


> +static int bmp580_nvmem_write(void *priv, unsigned int offset, void *val,
> +			      size_t bytes)
> +{
> +	struct bmp280_data *data = priv;
> +	int ret;
> +
> +	pm_runtime_get_sync(data->dev);
> +	ret = bmp580_nvmem_write_impl(priv, offset, val, bytes);
>  	pm_runtime_mark_last_busy(data->dev);
>  	pm_runtime_put_autosuspend(data->dev);
> +
>  	return ret;
>  }
> -

grump.

>  static int bmp580_preinit(struct bmp280_data *data)
>  {
>  	struct nvmem_config config = {


  reply	other threads:[~2024-05-19 14:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-12 23:05 [PATCH v7 0/5] iio: pressure: bmp280: Add triggered buffer support and Vasileios Amoiridis
2024-05-12 23:05 ` [PATCH v7 1/5] iio: pressure: bmp280: Refactorize reading functions Vasileios Amoiridis
2024-05-19 14:22   ` Jonathan Cameron
2024-05-12 23:05 ` [PATCH v7 2/5] iio: pressure: bmp280: Introduce new cleanup routines Vasileios Amoiridis
2024-05-19 14:24   ` Jonathan Cameron [this message]
2024-05-12 23:05 ` [PATCH v7 3/5] iio: pressure: bmp280: Generalize read_{temp,press,humid}() functions Vasileios Amoiridis
2024-05-19 14:28   ` Jonathan Cameron
2024-05-12 23:05 ` [PATCH v7 4/5] iio: pressure: bmp280: Add SCALE, RAW values in channels and refactorize them Vasileios Amoiridis
2024-05-19 14:30   ` Jonathan Cameron
2024-05-12 23:05 ` [PATCH v7 5/5] iio: pressure: bmp280: Add triggered buffer support Vasileios Amoiridis
2024-05-19 14:35   ` Jonathan Cameron
2024-05-29 20:12   ` Jonathan Cameron
2024-05-29 23:49     ` Vasileios Amoiridis

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=20240519152451.4e2782f5@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=579lpy@gmail.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=ak@it-klinger.de \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=ang.iglesiasg@gmail.com \
    --cc=lars@metafoo.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mazziesaccount@gmail.com \
    --cc=petre.rodan@subdimension.ro \
    --cc=phil@raspberrypi.com \
    --cc=semen.protsenko@linaro.org \
    --cc=vassilisamir@gmail.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