Re: linux-next: build warning after merge of the driver-core tree

[Rafael J. Wysocki]

On Wednesday, October 07, 2015 08:40:59 AM Viresh Kumar wrote:
> Hi Stephen,
> 
> On 7 October 2015 at 06:51, Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> wrote:
> > Hi Greg,
> >
> > After merging the driver-core tree, today's linux-next build (arm
> > multi_v7_defconfig) produced this warning:
> >
> > drivers/base/power/opp/debugfs.c: In function 'opp_debug_create_one':
> > drivers/base/power/opp/debugfs.c:48:7: warning: passing argument 4 of 'debugfs_create_bool' from incompatible pointer type
> >   if (!debugfs_create_bool("available", S_IRUGO, d,
> >        ^
> > In file included from drivers/base/power/opp/debugfs.c:13:0:
> > include/linux/debugfs.h:94:16: note: expected 'bool *' but argument is of type 'u32 *'
> >  struct dentry *debugfs_create_bool(const char *name, umode_t mode,
> >                 ^
> > drivers/base/power/opp/debugfs.c:52:7: warning: passing argument 4 of 'debugfs_create_bool' from incompatible pointer type
> >   if (!debugfs_create_bool("dynamic", S_IRUGO, d, (u32 *)&opp->dynamic))
> >        ^
> > In file included from drivers/base/power/opp/debugfs.c:13:0:
> > include/linux/debugfs.h:94:16: note: expected 'bool *' but argument is of type 'u32 *'
> >  struct dentry *debugfs_create_bool(const char *name, umode_t mode,
> >                 ^
> > drivers/base/power/opp/debugfs.c:55:7: warning: passing argument 4 of 'debugfs_create_bool' from incompatible pointer type
> >   if (!debugfs_create_bool("turbo", S_IRUGO, d, (u32 *)&opp->turbo))
> >        ^
> > In file included from drivers/base/power/opp/debugfs.c:13:0:
> > include/linux/debugfs.h:94:16: note: expected 'bool *' but argument is of type 'u32 *'
> >  struct dentry *debugfs_create_bool(const char *name, umode_t mode,
> >                 ^
> >
> > Introduced by commit
> >
> >   621a5f7ad9cd ("debugfs: Pass bool pointer to debugfs_create_bool()")
> >
> > interacting with commit
> >
> >   5cb5fdbf3877 ("PM / OPP: Add debugfs support")
> >
> > from the pm tree.
> 
> That was expected and the PM tree needs to get updated to get it fixed.
> And I will be doing that soon.

For the record, I'm tired of your breaking things on a regular basis like this.

I'm dropping 5cb5fdbf3877 from the PM tree.

Thanks,
Rafael

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/