linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Sebastian Reichel <sre@kernel.org>,
	Chanwoo Choi <cw00.choi@samsung.com>,
	Arnd Bergmann <arnd@arndb.de>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Ramakrishna Pallala <ramakrishna.pallala@intel.com>,
	Lee Jones <lee.jones@linaro.org>
Subject: Re: linux-next: build failure after merge of the extcon tree
Date: Fri, 5 Jun 2015 19:53:46 +0900	[thread overview]
Message-ID: <20150605105346.GD5346@kroah.com> (raw)
In-Reply-To: <20150604191838.26c8ac23@canb.auug.org.au>

On Thu, Jun 04, 2015 at 07:18:38PM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> This is now needed when the char-misc and battery trees are merged ...
> 
> On Mon, 25 May 2015 21:05:03 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > Hi all,
> > 
> > After merging the extcon tree, today's linux-next build (powerpc
> > allyesconfig) failed like this:
> > 
> > drivers/power/axp288_charger.c: In function 'axp288_charger_probe':
> > drivers/power/axp288_charger.c:851:8: error: incompatible type for argument 2 of 'extcon_register_notifier'
> >   ret = extcon_register_notifier(info->cable.edev, &info->cable.nb);
> >         ^
> > In file included from drivers/power/axp288_charger.c:29:0:
> > include/linux/extcon.h:240:12: note: expected 'enum extcon' but argument is of type 'struct notifier_block *'
> >  extern int extcon_register_notifier(struct extcon_dev *edev, enum extcon id,
> >             ^
> > drivers/power/axp288_charger.c:851:8: error: too few arguments to function 'extcon_register_notifier'
> >   ret = extcon_register_notifier(info->cable.edev, &info->cable.nb);
> >         ^
> > In file included from drivers/power/axp288_charger.c:29:0:
> > include/linux/extcon.h:240:12: note: declared here
> >  extern int extcon_register_notifier(struct extcon_dev *edev, enum extcon id,
> >             ^
> > drivers/power/axp288_charger.c:912:2: error: incompatible type for argument 2 of 'extcon_unregister_notifier'
> >   extcon_unregister_notifier(info->cable.edev, &info->cable.nb);
> >   ^
> > In file included from drivers/power/axp288_charger.c:29:0:
> > include/linux/extcon.h:242:12: note: expected 'enum extcon' but argument is of type 'struct notifier_block *'
> >  extern int extcon_unregister_notifier(struct extcon_dev *edev, enum extcon id,
> >             ^
> > drivers/power/axp288_charger.c:912:2: error: too few arguments to function 'extcon_unregister_notifier'
> >   extcon_unregister_notifier(info->cable.edev, &info->cable.nb);
> >   ^
> > In file included from drivers/power/axp288_charger.c:29:0:
> > include/linux/extcon.h:242:12: note: declared here
> >  extern int extcon_unregister_notifier(struct extcon_dev *edev, enum extcon id,
> >             ^
> > drivers/power/axp288_charger.c: In function 'axp288_charger_remove':
> > drivers/power/axp288_charger.c:923:2: error: incompatible type for argument 2 of 'extcon_unregister_notifier'
> >   extcon_unregister_notifier(info->cable.edev, &info->cable.nb);
> >   ^
> > In file included from drivers/power/axp288_charger.c:29:0:
> > include/linux/extcon.h:242:12: note: expected 'enum extcon' but argument is of type 'struct notifier_block *'
> >  extern int extcon_unregister_notifier(struct extcon_dev *edev, enum extcon id,
> >             ^
> > drivers/power/axp288_charger.c:923:2: error: too few arguments to function 'extcon_unregister_notifier'
> >   extcon_unregister_notifier(info->cable.edev, &info->cable.nb);
> >   ^
> > In file included from drivers/power/axp288_charger.c:29:0:
> > include/linux/extcon.h:242:12: note: declared here
> >  extern int extcon_unregister_notifier(struct extcon_dev *edev, enum extcon id,
> >             ^
> > 
> > Caused by commit 843735b788a4 ("power: axp288_charger: axp288 charger
> > driver") from the battery tree interacting with commit 046050f6e623
> > ("extcon: Update the prototype of extcon_register_notifier() with enum
> > extcon") from the extcon tree.
> > 
> > I applied this merge fix patch for tday and can carry it as necessary
> > (it is clearly not correct, but it will make it build):
> > 
> > From: Stephen Rothwell <sfr@canb.auug.org.au>
> > Date: Mon, 25 May 2015 21:00:24 +1000
> > Subject: [PATCH] power: axp288_charger: fix for AIP change
> > 
> > Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
> > ---
> >  drivers/power/axp288_charger.c | 6 +++---
> >  1 file changed, 3 insertions(+), 3 deletions(-)
> > 
> > diff --git a/drivers/power/axp288_charger.c b/drivers/power/axp288_charger.c
> > index 5680317f4823..e4d569f57acc 100644
> > --- a/drivers/power/axp288_charger.c
> > +++ b/drivers/power/axp288_charger.c
> > @@ -848,7 +848,7 @@ static int axp288_charger_probe(struct platform_device *pdev)
> >  	/* Register for extcon notification */
> >  	INIT_WORK(&info->cable.work, axp288_charger_extcon_evt_worker);
> >  	info->cable.nb.notifier_call = axp288_charger_handle_cable_evt;
> > -	ret = extcon_register_notifier(info->cable.edev, &info->cable.nb);
> > +	ret = extcon_register_notifier(info->cable.edev, EXTCON_NONE, &info->cable.nb);
> >  	if (ret) {
> >  		dev_err(&info->pdev->dev,
> >  			"failed to register extcon notifier %d\n", ret);
> > @@ -909,7 +909,7 @@ intr_reg_failed:
> >  		extcon_unregister_interest(&info->otg.cable);
> >  	power_supply_unregister(info->psy_usb);
> >  psy_reg_failed:
> > -	extcon_unregister_notifier(info->cable.edev, &info->cable.nb);
> > +	extcon_unregister_notifier(info->cable.edev, EXTCON_NONE, &info->cable.nb);
> >  	return ret;
> >  }
> >  
> > @@ -920,7 +920,7 @@ static int axp288_charger_remove(struct platform_device *pdev)
> >  	if (info->otg.cable.edev)
> >  		extcon_unregister_interest(&info->otg.cable);
> >  
> > -	extcon_unregister_notifier(info->cable.edev, &info->cable.nb);
> > +	extcon_unregister_notifier(info->cable.edev, EXTCON_NONE, &info->cable.nb);
> >  	power_supply_unregister(info->psy_usb);
> >  
> >  	return 0;

I think we are going to have to resolve this when it hits Linus's tree
:(

  reply	other threads:[~2015-06-05 10:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-25 11:05 linux-next: build failure after merge of the extcon tree Stephen Rothwell
2015-06-04  9:18 ` Stephen Rothwell
2015-06-05 10:53   ` Greg KH [this message]
2015-06-27  0:16     ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2019-07-19  0:48 Stephen Rothwell
2024-09-04  5:24 Stephen Rothwell
2024-09-04  9:24 ` Hans de Goede
2024-09-04 16:18   ` Chanwoo Choi
2025-05-06  6:22 Stephen Rothwell

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=20150605105346.GD5346@kroah.com \
    --to=greg@kroah.com \
    --cc=arnd@arndb.de \
    --cc=cw00.choi@samsung.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=ramakrishna.pallala@intel.com \
    --cc=sfr@canb.auug.org.au \
    --cc=sre@kernel.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).