From: William Breathitt Gray <vilhelm.gray@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Jarkko Nikula <jarkko.nikula@linux.intel.com>, linux-iio@vger.kernel.org
Subject: Re: [PATCH 1/2] counter: intel-qep: Mark PM callbacks with __maybe_unused
Date: Sat, 12 Jun 2021 09:45:41 +0900 [thread overview]
Message-ID: <YMQDtZ7o0MRvVdb9@shinobu> (raw)
In-Reply-To: <20210611182334.61133958@jic23-huawei>
[-- Attachment #1: Type: text/plain, Size: 2163 bytes --]
On Fri, Jun 11, 2021 at 06:23:34PM +0100, Jonathan Cameron wrote:
> On Fri, 11 Jun 2021 14:55:57 +0300
> Jarkko Nikula <jarkko.nikula@linux.intel.com> wrote:
>
> > Remove CONFIG_PM ifdef and mark PM callbacks with __maybe_unused.
> >
> > Suggested-by: Jonathan Cameron <jic23@kernel.org>
> > Signed-off-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>
>
> Both applied to the togreg branch of iio.git and pushed out
> as testing to let 0-day poke at them.
>
> William, if you want to give feedback on these, still time for
> me to add tags etc. They just seem trivial enough its not worth
> wasting your time :)
>
> Jonathan
Yes, these are pretty trivial and both look good to me. Feel free to add
my Ack to both patches if there's still time.
Acked-by: William Breathitt Gray <vilhelm.gray@gmail.com>
> > ---
> > drivers/counter/intel-qep.c | 6 ++----
> > 1 file changed, 2 insertions(+), 4 deletions(-)
> >
> > diff --git a/drivers/counter/intel-qep.c b/drivers/counter/intel-qep.c
> > index ab10ba33f46a..a8d3dccecc0f 100644
> > --- a/drivers/counter/intel-qep.c
> > +++ b/drivers/counter/intel-qep.c
> > @@ -473,8 +473,7 @@ static void intel_qep_remove(struct pci_dev *pci)
> > intel_qep_writel(qep, INTEL_QEPCON, 0);
> > }
> >
> > -#ifdef CONFIG_PM
> > -static int intel_qep_suspend(struct device *dev)
> > +static int __maybe_unused intel_qep_suspend(struct device *dev)
> > {
> > struct pci_dev *pdev = container_of(dev, struct pci_dev, dev);
> > struct intel_qep *qep = pci_get_drvdata(pdev);
> > @@ -486,7 +485,7 @@ static int intel_qep_suspend(struct device *dev)
> > return 0;
> > }
> >
> > -static int intel_qep_resume(struct device *dev)
> > +static int __maybe_unused intel_qep_resume(struct device *dev)
> > {
> > struct pci_dev *pdev = container_of(dev, struct pci_dev, dev);
> > struct intel_qep *qep = pci_get_drvdata(pdev);
> > @@ -512,7 +511,6 @@ static int intel_qep_resume(struct device *dev)
> >
> > return 0;
> > }
> > -#endif
> >
> > static UNIVERSAL_DEV_PM_OPS(intel_qep_pm_ops,
> > intel_qep_suspend, intel_qep_resume, NULL);
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2021-06-12 0:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 11:55 [PATCH 1/2] counter: intel-qep: Mark PM callbacks with __maybe_unused Jarkko Nikula
2021-06-11 11:55 ` [PATCH 2/2] counter: intel-qep: Use to_pci_dev() helper Jarkko Nikula
2021-06-13 10:36 ` Andy Shevchenko
2021-06-13 11:08 ` Jonathan Cameron
2021-06-14 8:24 ` Jarkko Nikula
2021-06-14 8:57 ` Andy Shevchenko
2021-06-14 9:37 ` Uwe Kleine-König
2021-06-14 10:47 ` Jonathan Cameron
2021-06-14 11:10 ` Andy Shevchenko
2021-06-11 17:23 ` [PATCH 1/2] counter: intel-qep: Mark PM callbacks with __maybe_unused Jonathan Cameron
2021-06-12 0:45 ` William Breathitt Gray [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=YMQDtZ7o0MRvVdb9@shinobu \
--to=vilhelm.gray@gmail.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
/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