Re: [PATCH 0/3] check regulator_enable() return value

2013-04-03 Thread Felipe Balbi
Hi, On Wed, Apr 03, 2013 at 07:22:38AM -0700, Greg KH wrote: > On Wed, Apr 03, 2013 at 05:06:22PM +0300, Felipe Balbi wrote: > > Hi, > > > > On Wed, Apr 03, 2013 at 04:02:24PM +0200, Fabio Baltieri wrote: > > > While testing your 'next' branch merged with today's next I got some new > > > warning

Re: [PATCH 0/3] check regulator_enable() return value

2013-04-03 Thread Greg KH
On Wed, Apr 03, 2013 at 05:06:22PM +0300, Felipe Balbi wrote: > Hi, > > On Wed, Apr 03, 2013 at 04:02:24PM +0200, Fabio Baltieri wrote: > > While testing your 'next' branch merged with today's next I got some new > > warnings, caused by a recently introduced __must_check in: > > > > c8801a8 regul

Re: [PATCH 0/3] check regulator_enable() return value

2013-04-03 Thread Fabio Baltieri
Hi Felipe, On Wed, Apr 03, 2013 at 05:06:22PM +0300, Felipe Balbi wrote: > Hi, > > On Wed, Apr 03, 2013 at 04:02:24PM +0200, Fabio Baltieri wrote: > > While testing your 'next' branch merged with today's next I got some new > > warnings, caused by a recently introduced __must_check in: > > > > c

Re: [PATCH 0/3] check regulator_enable() return value

2013-04-03 Thread Felipe Balbi
Hi, On Wed, Apr 03, 2013 at 04:02:24PM +0200, Fabio Baltieri wrote: > While testing your 'next' branch merged with today's next I got some new > warnings, caused by a recently introduced __must_check in: > > c8801a8 regulator: core: Mark all get and enable calls as __must_check > > These patches