public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: slash.tmp@free•fr (Mason)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v3] thermal: tango: add resume support
Date: Wed, 24 Aug 2016 17:12:22 +0200	[thread overview]
Message-ID: <57BDB956.8020709@free.fr> (raw)
In-Reply-To: <2198269.vtL6N6bMEV@wuerfel>

On 24/08/2016 10:32, Arnd Bergmann wrote:

> I think the ideal is to have only one set of conditionals in each
> driver, so at least you don't get a mismatch between them.
> 
> SIMPLE_DEV_PM_OPS uses conditional evaluation (but does not
> show the reference to the compiler). Annotating the functions as
> __maybe_unused lets the compiler decide for itself if they should
> be dropped or not, which means we use only the conditional inside
> of SIMPLE_DEV_PM_OPS.
> 
> Ideally, SIMPLE_DEV_PM_OPS itself should have used an IS_ENABLED()
> check instead of the #ifdef, that would have made it possible to
> just leave the function always defined with no __maybe_unused, but
> still have it dropped from the object code without a warning
> when there is no runtime reference.

I'm not sure my trivial issue deserves this much discussion. I just
want the patch to be upstream in some form.

I'll submit one more patch, with SIMPLE_DEV_PM_OPS used unconditionally,
and annotate the resume function with __maybe_unused.

This will waste the space of the struct on systems where S3 is disabled,
but it seems to be the preferred solution, IIUC.

Regards.

  reply	other threads:[~2016-08-24 15:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-28 11:37 [RESEND PATCH v2] thermal: tango: add resume support Mason
2016-07-18  9:33 ` Thierry Reding
2016-07-18 10:09   ` Arnd Bergmann
2016-07-18 10:13     ` Thierry Reding
2016-07-18 11:10       ` Arnd Bergmann
2016-07-18 11:28         ` Thierry Reding
2016-07-18 12:21 ` [PATCH v3] " Mason
2016-07-20 10:50   ` Thierry Reding
2016-07-22 22:00   ` Kevin Hilman
2016-07-25  8:18     ` Mason
2016-07-25  8:52       ` Arnd Bergmann
2016-07-25  9:48         ` Mason
2016-07-26 12:13           ` Arnd Bergmann
2016-08-19 11:29             ` Zhang Rui
2016-08-22 21:00               ` Arnd Bergmann
2016-08-24  8:25                 ` Zhang Rui
2016-08-24  8:32                   ` Arnd Bergmann
2016-08-24 15:12                     ` Mason [this message]
2016-09-02 13:17 ` [PATCH v4] " Marc Gonzalez
2016-09-02 20:54   ` Kevin Hilman

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=57BDB956.8020709@free.fr \
    --to=slash.tmp@free$(echo .)fr \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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