[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091121234509.GC1411@ucw.cz>
Date: Sun, 22 Nov 2009 00:45:10 +0100
From: Pavel Machek <pavel@....cz>
To: Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc: Linux-pm mailing list <linux-pm@...ts.osdl.org>,
kernel list <linux-kernel@...r.kernel.org>
Subject: Re: [linux-pm] Null suspend/resume functions
On Thu 2009-11-19 11:21:03, Mark Brown wrote:
> On Wed, Nov 18, 2009 at 05:09:08PM +0100, Pavel Machek wrote:
> > On Tue 2009-11-17 12:41:25, Mark Brown wrote:
>
> > > The problem I have with that is that for most APIs noop functions are a
> > > big fat warning sign that something is going wrong and the API is being
> > > abused. This then creates noise and code review problems in the driver
> > > code since you've got something that normally suggests a problem.
>
> > That still sounds like poor reason to add tests to core. But return 0
> > function for that purpose should be ok (and should make code easy to
> > review, too).
>
> What makes you believe that this is a poor reason? The issue isn't that
> the driver code is complex, the issue is that it's noise in the driver
> which suggests that the driver isn't doing something it's supposed to
> do.
So you place a comment there; it should be there anyway. Having nop
during suspend/resume *is* unusual, and it should raise red flags.
Plus, if we allowed NULLs there, we'd not know if the driver does not
implement it because it is not neccessary, or because they don't care.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
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/
Powered by blists - more mailing lists