[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170629144927.GP29665@vireshk-i7>
Date: Thu, 29 Jun 2017 20:19:27 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Russell King - ARM Linux <linux@...linux.org.uk>
Cc: Randy Dunlap <rdunlap@...radead.org>,
Rafael Wysocki <rjw@...ysocki.net>,
Vincent Guittot <vincent.guittot@...aro.org>,
Rob Herring <robh@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Stephen Boyd <sboyd@...eaurora.org>,
linux-kernel@...r.kernel.org, Mark Brown <broonie@...nel.org>,
rnayak@...eaurora.org, Shiraz Hashim <shashim@...eaurora.org>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [RFC 1/5] drivers: Add boot constraints core
On 29-06-17, 13:50, Russell King - ARM Linux wrote:
> On Thu, Jun 29, 2017 at 09:21:57AM +0530, Viresh Kumar wrote:
> > On 28-06-17, 08:55, Randy Dunlap wrote:
> > > On 06/28/2017 03:26 AM, Viresh Kumar wrote:
> >
> > > > +config BOOT_CONSTRAINTS
> > > > + bool "Boot constraints for devices"
> > > > + default y
> > >
> > > Why default y?
> > >
> > > As Linus just wrote yesterday:
> > >
> > > No. We've tried. The only sensible default (and that I try to enforce)
> > > is "new featrures default to 'n'"
> >
> > Yeah, this should have been n really.
>
> Given that the default default is to default to n, you don't need to
> supply a default that just says what the default default actually is.
> Please also avoid silly defaults.
That was nice :)
Yeah, will get rid of the default statement here.
--
viresh
Powered by blists - more mailing lists