From: Greg KH <greg@kroah.com>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: Nick Warne <nick@linicks.net>, linux-kernel@vger.kernel.org
Subject: Re: Still get build warnings - gcc-3.4.6 - 2.6.17.8
Date: Tue, 8 Aug 2006 16:19:15 -0700 [thread overview]
Message-ID: <20060808231915.GA23161@kroah.com> (raw)
In-Reply-To: <20060808141246.25ee5db7.rdunlap@xenotime.net>
On Tue, Aug 08, 2006 at 02:12:46PM -0700, Randy.Dunlap wrote:
> On Tue, 8 Aug 2006 21:48:11 +0100 Nick Warne wrote:
>
> > Hi all,
> >
> > I have had these warnings for ages:
> >
> > kernel/power/pm.c:241: warning: `pm_register' is deprecated (declared at
> > kernel/power/pm.c:64)
> > kernel/power/pm.c:241: warning: `pm_register' is deprecated (declared at
> > kernel/power/pm.c:64)
> > kernel/power/pm.c:242: warning: `pm_unregister_all' is deprecated (declared at
> > kernel/power/pm.c:97)
> > kernel/power/pm.c:242: warning: `pm_unregister_all' is deprecated (declared at
> > kernel/power/pm.c:97)
> > kernel/power/pm.c:243: warning: `pm_send_all' is deprecated (declared at
> > kernel/power/pm.c:216)
> > kernel/power/pm.c:243: warning: `pm_send_all' is deprecated (declared at
> > kernel/power/pm.c:216)
> >
> > and I think at one time there was a fix about that I applied, but it seems it
> > never made it into kernel.org.
> >
> > Or is this my ggc problem?
>
> It's not a gcc (nor ggc) problem. Those functions are just deprecated.
> Current 2.6.18-rc4 and 2.6.18-rc3-mm2 still have those same warnings.
>
> fwiw, I don't seem to have any patches to fix/remove them.
pm_unregister_all is removed in the -mm tree, from a patch in my tree.
thanks,
greg k-h
next prev parent reply other threads:[~2006-08-08 23:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-08 20:48 Still get build warnings - gcc-3.4.6 - 2.6.17.8 Nick Warne
2006-08-08 21:12 ` Randy.Dunlap
2006-08-08 22:15 ` Sam Ravnborg
2006-08-08 23:19 ` Greg KH [this message]
2006-08-09 17:38 ` Nick Warne
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=20060808231915.GA23161@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@linicks.net \
--cc=rdunlap@xenotime.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.