linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: balbi@ti.com
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	WingMan Kwok <w-kwok2@ti.com>, Roger Quadros <rogerq@ti.com>
Subject: Re: linux-next: build failure after merge of the usb-gadget tree
Date: Tue, 17 Dec 2013 10:10:32 +1100	[thread overview]
Message-ID: <20131217101032.1f4d2ba671e6359fce0514cb@canb.auug.org.au> (raw)
In-Reply-To: <20131216194113.GA5258@saruman.home>

[-- Attachment #1: Type: text/plain, Size: 2045 bytes --]

Hi Felipe,

On Mon, 16 Dec 2013 13:41:13 -0600 Felipe Balbi <balbi@ti.com> wrote:
>
> On Mon, Dec 16, 2013 at 03:40:20PM +1100, Stephen Rothwell wrote:
> > 
> > After merging the usb-gadget tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> > 
> > drivers/usb/phy/phy-keystone.c: In function 'keystone_usbphy_probe':
> > drivers/usb/phy/phy-keystone.c:96:4: warning: passing argument 3 of 'usb_phy_gen_create_phy' makes pointer from integer without a cast [enabled by default]
> >     USB_PHY_TYPE_USB2, 0, false);
> >     ^
> > In file included from drivers/usb/phy/phy-keystone.c:25:0:
> > drivers/usb/phy/phy-generic.h:18:5: note: expected 'struct usb_phy_gen_xceiv_platform_data *' but argument is of type 'int'
> >  int usb_phy_gen_create_phy(struct device *dev, struct usb_phy_gen_xceiv *nop,
> >      ^
> > drivers/usb/phy/phy-keystone.c:96:4: error: too many arguments to function 'usb_phy_gen_create_phy'
> >     USB_PHY_TYPE_USB2, 0, false);
> >     ^
> > In file included from drivers/usb/phy/phy-keystone.c:25:0:
> > drivers/usb/phy/phy-generic.h:18:5: note: declared here
> >  int usb_phy_gen_create_phy(struct device *dev, struct usb_phy_gen_xceiv *nop,
> >      ^
> > 
> > Caused by commit 25acdd08fd71 ("usb: phy: add Keystone usb phy driver")
> > interacting with commit bd27fa44e138 ("usb: phy: add Keystone usb phy
> > driver") which was merged before v3.13-rc1 and is included in the
> > usb-gadget tree.
> 
> I cannot see how those commits would cause the error above. I have
> recompiled my tree with allmodconfig (x86 and ARM) config and
> omap2plus_defconfig (adding COMPILE_TEST and enabling KEYSTONE PHY) and
> cannot see this error.
> 
> Maybe someone applied a drivers/usb/phy/ patch ahead of me ?

That would be your patch (af9f51c5512f "usb: phy: generic: fix how we find
out about our resources") that went into v3.13-rc4 ...

Can you send me a suitable merge fixup, please?
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-12-16 23:10 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-16  4:40 linux-next: build failure after merge of the usb-gadget tree Stephen Rothwell
2013-12-16 19:41 ` Felipe Balbi
2013-12-16 23:10   ` Stephen Rothwell [this message]
2013-12-16 23:38     ` Felipe Balbi
2013-12-17  4:27       ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2020-03-16  3:37 Stephen Rothwell
2020-03-16 17:42 ` John Stultz
2020-03-16 18:11   ` John Stultz
2020-03-16 19:46     ` Greg KH
2015-05-29  8:32 Stephen Rothwell
2015-05-29 15:19 ` Felipe Balbi
2013-12-09  3:58 Stephen Rothwell
2013-12-09  4:11 ` Felipe Balbi
2013-12-09 19:40   ` Felipe Balbi
2013-12-09 20:43     ` Stephen Rothwell
2013-12-09 21:01       ` Felipe Balbi
2013-12-09 21:42         ` Felipe Balbi
2013-12-17  4:36   ` Stephen Rothwell
2013-12-17  5:08     ` Felipe Balbi
2013-12-17  5:13       ` Felipe Balbi
2013-07-30  4:34 Stephen Rothwell
2013-07-30  5:49 ` Felipe Balbi

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=20131217101032.1f4d2ba671e6359fce0514cb@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=balbi@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rogerq@ti.com \
    --cc=w-kwok2@ti.com \
    /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).