linux-kernel - Converting to dev_pm_ops (remove annoying warnings)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090728104434.GA1728@fluff.org.uk>
Date:	Tue, 28 Jul 2009 11:44:34 +0100
From:	Ben Dooks <ben-linux@...ff.org>
To:	linux-kernel@...r.kernel.org
Cc:	linux-pm@...ts.linux-foundation.org
Subject: Converting to dev_pm_ops (remove annoying warnings)

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@...ff.org, http://www.fluff.org/)

  'a smiley only costs 4 bytes'
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/