linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Coiby Xu <coiby.xu@gmail.com>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
	Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
	linux-iio@vger.kernel.org (open list:IIO SUBSYSTEM AND DRIVERS),
	linux-kernel@vger.kernel.org (open list)
Subject: Re: [PATCH 01/15] iio: accel: remove unnecessary CONFIG_PM_SLEEP
Date: Thu, 29 Oct 2020 14:40:07 +0000	[thread overview]
Message-ID: <20201029144007.77d967b0@archlinux> (raw)
In-Reply-To: <20201029074910.227859-1-coiby.xu@gmail.com>

On Thu, 29 Oct 2020 15:48:56 +0800
Coiby Xu <coiby.xu@gmail.com> wrote:

> SIMPLE_DEV_PM_OPS has already took good care of CONFIG_PM_CONFIG.
> 
> Signed-off-by: Coiby Xu <coiby.xu@gmail.com>
Hi Coiby, 

Please put a cover letter on your next series explaining the context.
In this particular case some of the replies you have gotten are
general at it is a lot easier to find these sorts of things via
replying to the cover letter.

Jonathan

> ---
>  drivers/iio/accel/da311.c | 2 --
>  1 file changed, 2 deletions(-)
> 
> diff --git a/drivers/iio/accel/da311.c b/drivers/iio/accel/da311.c
> index 3b3df620ba27..55d4891556ca 100644
> --- a/drivers/iio/accel/da311.c
> +++ b/drivers/iio/accel/da311.c
> @@ -263,7 +263,6 @@ static int da311_remove(struct i2c_client *client)
>  	return da311_enable(client, false);
>  }
>  
> -#ifdef CONFIG_PM_SLEEP
>  static int da311_suspend(struct device *dev)
>  {
>  	return da311_enable(to_i2c_client(dev), false);
> @@ -273,7 +272,6 @@ static int da311_resume(struct device *dev)
>  {
>  	return da311_enable(to_i2c_client(dev), true);
>  }
> -#endif
>  
>  static SIMPLE_DEV_PM_OPS(da311_pm_ops, da311_suspend, da311_resume);
>  


  parent reply	other threads:[~2020-10-29 14:40 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-29  7:48 [PATCH 01/15] iio: accel: remove unnecessary CONFIG_PM_SLEEP Coiby Xu
2020-10-29  7:48 ` [PATCH 02/15] " Coiby Xu
2020-10-29  7:48 ` [PATCH 03/15] " Coiby Xu
2020-10-29  7:48 ` [PATCH 04/15] " Coiby Xu
2020-10-29  7:49 ` [PATCH 05/15] " Coiby Xu
2020-10-29 11:57   ` Andy Shevchenko
2020-10-29 14:41     ` Coiby Xu
2020-10-29  7:49 ` [PATCH 06/15] " Coiby Xu
2020-10-29  7:49 ` [PATCH 07/15] iio: ssp: " Coiby Xu
2020-10-29  7:49 ` [PATCH 08/15] iio: magnetometer: mmc35240: " Coiby Xu
2020-10-29  7:49 ` [PATCH 09/15] iio: adc: palmas_gpadc: " Coiby Xu
2020-10-29  7:49 ` [PATCH 10/15] iio: adc: stm32: " Coiby Xu
2020-10-29 11:31   ` Fabrice Gasnier
2020-10-29  7:49 ` [PATCH 11/15] iio: adc: at91_adc: " Coiby Xu
2020-10-29  7:49 ` [PATCH 12/15] iio: imu: kmx61: " Coiby Xu
2020-10-29  7:49 ` [PATCH 13/15] iio: light: us5182d: " Coiby Xu
2020-10-29  7:49 ` [PATCH 14/15] iio: light: " Coiby Xu
2020-10-29  7:49 ` [PATCH 15/15] iio: proximity: " Coiby Xu
2020-10-29 14:40 ` Jonathan Cameron [this message]
2020-10-29 14:43   ` [PATCH 01/15] iio: accel: " Coiby Xu
2020-10-29 17:06   ` Andy Shevchenko
2020-10-30 14:34     ` Coiby Xu
2020-10-31 11:05       ` Jonathan Cameron
2020-10-31 22:47         ` Coiby Xu
2020-11-01 17:20           ` Jonathan Cameron

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=20201029144007.77d967b0@archlinux \
    --to=jic23@kernel.org \
    --cc=coiby.xu@gmail.com \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmeerw@pmeerw.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;
as well as URLs for NNTP newsgroup(s).