From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
David Woodhouse <dwmw2@infradead.org>,
Alan Stern <stern@rowland.harvard.edu>,
Andrew Morton <akpm@osdl.org>, Greg KH <greg@kroah.com>,
Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PATCH] More PCI patches for 2.6.13
Date: Sat, 10 Sep 2005 23:32:54 +0100 [thread overview]
Message-ID: <200509102332.54619.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <43235707.7050909@pobox.com>
On Saturday 10 September 2005 22:58, Jeff Garzik wrote:
> Linus Torvalds wrote:
> > Case closed.
> >
> > Bogus warnings are a _bad_ thing. They cause people to write buggy code.
> >
> > That drivers/pci/pci.c code should be simplified to not look at the error
> > return from pci_set_power_state() at all. Special-casing EIO is just
> > another bug waiting to happen.
>
> As a tangent, the 'foo is deprecated' warnings for pm_register() and
> inter_module_register() annoy me, primarily because they never seem to
> go away.
>
> The only user of inter_module_xxx is CONFIG_MTD -- thus the deprecated
> warning is useless to 90% of us, who will never use MTD. As for
> pm_register(), there are tons of users remaining. As such, for the
> forseeable future, we will continue to see pm_register() warnings and
> ignore them -- thus they are nothing but useless build noise.
>
> I've attached a patch, just tested, which addresses inter_module_xxx by
> making its build conditional on the last remaining user. This solves
> the deprecated warning problem for most of us, and makes the kernel
> smaller for most of us, at the same time.
Though external modules using these functions will be hung out to dry. But
only if you don't select CONFIG_MTD? That's not particularly intuitive.
It's better to mark it deprecated (which has been done), then officially
remove it (and all in-tree users) once and for all. Compiling the code
conditionally just to avoid a few warnings is a silly idea.
--
Cheers,
Alistair.
'No sense being pessimistic, it probably wouldn't work anyway.'
Third year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
next prev parent reply other threads:[~2005-09-10 22:32 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-10 21:07 Alan Stern
2005-09-10 21:12 ` Linus Torvalds
2005-09-10 21:58 ` Jeff Garzik
2005-09-10 22:31 ` Andrew Morton
2005-09-10 22:53 ` Linus Torvalds
2005-09-10 23:44 ` Jeff Garzik
2005-09-11 0:02 ` Linus Torvalds
2005-09-11 0:17 ` Jeff Garzik
2005-09-11 0:27 ` Linus Torvalds
2005-09-10 23:02 ` Pavel Machek
2005-09-11 11:38 ` Pavel Machek
2005-09-10 22:32 ` Alistair John Strachan [this message]
2005-09-10 23:47 ` Jeff Garzik
2005-09-11 6:47 ` David Woodhouse
2005-09-11 4:41 ` Greg KH
2005-09-11 6:47 ` Alistair John Strachan
-- strict thread matches above, loose matches on Subject: below --
2005-09-11 2:34 Gabriel A. Devenyi
2005-09-09 22:07 Greg KH
2005-09-09 22:37 ` Linus Torvalds
2005-09-09 22:54 ` Greg KH
2005-09-09 23:22 ` Linus Torvalds
2005-09-09 23:28 ` Linus Torvalds
2005-09-09 23:36 ` Andrew Morton
2005-09-10 0:22 ` Linus Torvalds
2005-09-10 1:27 ` Jeff Garzik
2005-09-10 18:33 ` John W. Linville
2005-09-10 18:53 ` Linus Torvalds
2005-09-11 11:33 ` Pavel Machek
2005-09-10 10:05 ` Arjan van de Ven
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=200509102332.54619.s0348365@sms.ed.ac.uk \
--to=s0348365@sms.ed.ac.uk \
--cc=akpm@osdl.org \
--cc=dwmw2@infradead.org \
--cc=greg@kroah.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®