public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Dooks <ben-linux@fluff.org>
To: linux-kernel@vger.kernel.org
Cc: linux-pm@lists.linux-foundation.org
Subject: Converting to dev_pm_ops (remove annoying warnings)
Date: Tue, 28 Jul 2009 11:44:34 +0100	[thread overview]
Message-ID: <20090728104434.GA1728@fluff.org.uk> (raw)

I have a couple of questions about changing drivers to use the
dev_pm_ops method within drivers using the device driver model.

1) Should the suspend/resume code still be wrapped in #ifdef CONFIG_PM
   and supply a NULL 'struct dev_pm_ops' wen CONFIG_PM=n

2) Is it allowable to submit changes to move drivers to dev_pm_ops
   during the -rc phase, or do we have to wait for the merge window
   before sending these? The number of warnings on a system that
   relies heavily on platform devices is annoying (S3C24XX ARM).

-- 
Ben (ben@fluff.org, http://www.fluff.org/)

  'a smiley only costs 4 bytes'

             reply	other threads:[~2009-07-28 10:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-28 10:44 Ben Dooks [this message]
2009-08-03  3:15 ` Converting to dev_pm_ops (remove annoying warnings) Magnus Damm

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=20090728104434.GA1728@fluff.org.uk \
    --to=ben-linux@fluff.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.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