linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Viresh Kumar <viresh.kumar@linaro.org>, Greg KH <greg@kroah.com>,
	linux-next list <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the driver-core tree
Date: Thu, 08 Oct 2015 00:47:36 +0200	[thread overview]
Message-ID: <1846544.jnahGernn9@vostro.rjw.lan> (raw)
In-Reply-To: <20151008090427.61690eef@canb.auug.org.au>

On Thursday, October 08, 2015 09:04:27 AM Stephen Rothwell wrote:
> Hi Rafael,
> 
> On Wed, 07 Oct 2015 23:48:11 +0200 "Rafael J. Wysocki" <rjw@rjwysocki.net> wrote:
> >
> > On Wednesday, October 07, 2015 08:40:59 AM Viresh Kumar wrote:
> > > 
> > > On 7 October 2015 at 06:51, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > > >
> > > > 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.
> 
> To be fair, this is caused by in interaction between your tree and
> Greg's ... i.e. the API for debugfs_create_bool() was updated in Greg's
> tree while a new use of it was added to your tree.  It can only be
> fixed by one of you merging the other's tree (or part of it) or by
> someone giving me a merge resolution patch (or just a hint) and me
> carrying that (and someone remembering to tell Linus about it.

Well, the conflicting commits here were from the same developer which is kind
of annoying.

The new use in my tree can wait until the API update in the Greg's tree is
merged IMO.  That's why I've now dropped the commit that added it. :-)

Thanks,
Rafael


  reply	other threads:[~2015-10-07 22:19 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-07  4:51 linux-next: build warning after merge of the driver-core tree Stephen Rothwell
2015-10-07  6:40 ` Viresh Kumar
2015-10-07 21:48   ` Rafael J. Wysocki
2015-10-07 22:04     ` Stephen Rothwell
2015-10-07 22:47       ` Rafael J. Wysocki [this message]
2015-10-08  7:09         ` Viresh Kumar
2015-10-08 20:30           ` Rafael J. Wysocki
2015-10-09  5:36             ` Stephen Rothwell
2015-10-09  6:31               ` Viresh Kumar
2015-10-09 20:49                 ` Rafael J. Wysocki
2015-10-09  6:37             ` Viresh Kumar
  -- strict thread matches above, loose matches on Subject: below --
2023-03-27  1:03 Stephen Rothwell
2023-03-27  7:31 ` Greg KH
2023-02-20  5:31 Stephen Rothwell
2023-02-20  7:26 ` Qi Zheng
2023-02-20  7:31   ` Greg KH
2023-02-20  9:49     ` Bagas Sanjaya
2023-02-20 10:15       ` Qi Zheng
2023-02-20 10:50         ` Greg KH
2023-02-20 11:01           ` Qi Zheng
2022-05-01 22:36 Stephen Rothwell
2021-12-06  8:30 Stephen Rothwell
2021-12-06 12:53 ` Heiko Carstens
2021-12-07 10:23 ` Greg KH
2020-09-09  7:23 Stephen Rothwell
2020-09-09  7:40 ` Greg KH
2019-08-05  3:04 Stephen Rothwell
2019-08-05  4:56 ` Stephen Rothwell
2019-08-06  0:03   ` Saravana Kannan
2019-08-01  5:05 Stephen Rothwell
2019-08-01  6:10 ` Greg KH
2019-07-04  6:24 Stephen Rothwell
2019-07-04  8:21 ` Greg KH
2019-07-04  6:17 Stephen Rothwell
2019-07-04  6:30 ` Greg KH
2013-06-25  8:33 Stephen Rothwell
2013-06-25 12:00 ` Ming Lei
2011-02-21  6:02 Stephen Rothwell
2011-02-21  6:32 ` Greg KH
2011-02-21 20:18 ` Ilya Yanok
2011-02-21  5:37 Stephen Rothwell
2011-02-21  5:50 ` Stephen Rothwell
2011-02-21  6:31   ` Greg KH
2011-03-17 23:10   ` Stephen Rothwell
2010-09-02  3:18 Stephen Rothwell
2010-09-02  3:29 ` Greg KH
2010-09-02 10:14   ` Thomas Renninger
2010-09-02 19:59     ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1846544.jnahGernn9@vostro.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=viresh.kumar@linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).