[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170210212432.GA7711@amd>
Date: Fri, 10 Feb 2017 22:24:32 +0100
From: Pavel Machek <pavel@....cz>
To: Viresh Kumar <viresh.kumar@...aro.org>
Cc: Rafael Wysocki <rjw@...ysocki.net>, khilman@...libre.com,
ulf.hansson@...aro.org, Len Brown <len.brown@...el.com>,
linaro-kernel@...ts.linaro.org, linux-pm@...r.kernel.org,
linux-kernel@...r.kernel.org,
Vincent Guittot <vincent.guittot@...aro.org>,
sboyd@...eaurora.org, nm@...com, robh+dt@...nel.org,
lina.iyer@...aro.org, rnayak@...eaurora.org
Subject: Re: [PATCH V2 1/6] PM / QOS: Add default case to the switch
On Fri 2017-02-10 11:30:30, Viresh Kumar wrote:
> On 09-02-17, 15:24, Pavel Machek wrote:
> > On Thu 2017-02-09 09:11:47, Viresh Kumar wrote:
> > > The switch block handles all the QOS request types present today, but
> > > starts giving compilation warnings as soon as a new type is added and
> > > not handled in this.
> > >
> > > To prevent against that, add the default case as well and do a WARN from
> > > it.
> >
> > I'd say compilation-time warning is better than hmm.... stacktrace and memory leak
> > at runtime?
>
> Of course we aren't going to allow a compilation warning for each and every
> platform that compiles this file. How do you wish to fix the issue then ?
Surely compilation warnings are better than getting bug reports from
users?
Of course, it is better to fix the switch when adding new QoS type...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Download attachment "signature.asc" of type "application/pgp-signature" (182 bytes)
Powered by blists - more mailing lists