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
> > >
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
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:
> >
> >
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
Hello Felipe,
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 introduces a check for regulator_enable() return value in
all
Hello Felipe,
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 introduces a check for regulator_enable() return value in
all
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
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:
c8801a8
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 regulator:
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
warnings, caused by
10 matches
Mail list logo