From: David McCullough <davidm@snapgear.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@zip.com.au>,
Linus Torvalds <torvalds@osdl.org>,
vojtech@suse.cz, dwmw2@infradead.org, netdev@vger.kernel.org,
benjamin_kong@ali.com.tw, dagb@cs.uit.no, jgarzik@pobox.com,
twoller@crystal.cirrus.com, alan@redhat.com, mm@caldera.de,
scott@spiteful.org, jsimmons@transvirtual.com
Subject: Re: pm_register should die
Date: Tue, 13 Sep 2005 10:03:35 +1000 [thread overview]
Message-ID: <20050913000335.GA10418@beast> (raw)
In-Reply-To: <20050912093456.GA29205@elf.ucw.cz>
Jivin Pavel Machek lays it down ...
> Hi!
>
> pm_register has been obsoleted by driver model, and it was deprecated
> quite long time ago. There are only 13 users left.
>
> Attached is a patch that makes pm_register config-option, so that we
> don't get the warnings on sane systems. Pretty please, remove usage of
> pm_register from your subsystem.
>
> IRDA has no usefull MAINTAINER entry; it would be nice if that could
> be fixed. Alan is best contact I could find for ad1848... does someone
> care about that driver, anyway? nm256_audio is written by
> anonymous. Wonderfull...
>
> Okay, it seems to me only users that matter are mtdcore, 3c509 and
> maybe h3600_ts_input. After those are fixed, it should be okay to just
> config it out/remove pm_register completely.
Feel free to clean out pm_register usage in:
drivers/serial/68328serial.c
there's not much in there that cannot be added later if actually required,
Cheers,
Davidm
--
David McCullough, davidm@cyberguard.com.au, Custom Embedded Solutions + Security
Ph:+61 734352815 Fx:+61 738913630 http://www.uCdot.org http://www.cyberguard.com
next prev parent reply other threads:[~2005-09-13 0:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-12 9:34 pm_register should die Pavel Machek
2005-09-12 9:41 ` Andrew Morton
2005-09-12 9:53 ` Pavel Machek
2005-09-12 9:55 ` Pavel Machek
2005-09-12 10:03 ` Andrew Morton
2005-09-13 0:03 ` David McCullough [this message]
2005-09-13 1:32 ` Alan Cox
2005-09-13 12:12 ` Pavel Machek
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=20050913000335.GA10418@beast \
--to=davidm@snapgear.com \
--cc=akpm@zip.com.au \
--cc=alan@redhat.com \
--cc=benjamin_kong@ali.com.tw \
--cc=dagb@cs.uit.no \
--cc=dwmw2@infradead.org \
--cc=jgarzik@pobox.com \
--cc=jsimmons@transvirtual.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm@caldera.de \
--cc=netdev@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=scott@spiteful.org \
--cc=torvalds@osdl.org \
--cc=twoller@crystal.cirrus.com \
--cc=vojtech@suse.cz \
/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).