linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@kernel.org>
To: Greg KH <greg@kroah.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Pawel Laszczak <pawell@cadence.com>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the usb and usb-gadget trees
Date: Thu, 4 Jul 2019 10:28:34 +0300	[thread overview]
Message-ID: <CAH8TKc_4ggxOPgii8gLGo2d7nvx08cbTk8_xDUQfA2Ckcxb_Aw@mail.gmail.com> (raw)
In-Reply-To: <20190704065949.GA32707@kroah.com>

Hi,

On Thu, Jul 4, 2019 at 9:59 AM Greg KH <greg@kroah.com> wrote:
>
> On Thu, Jul 04, 2019 at 04:34:58PM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the usb tree, today's linux-next build (arm
> > multi_v7_defconfig) failed like this:
> >
> > arm-linux-gnueabi-ld: drivers/usb/dwc3/trace.o: in function `trace_raw_output_dwc3_log_ctrl':
> > trace.c:(.text+0x119c): undefined reference to `usb_decode_ctrl'
> >
> > Caused by commit
> >
> >   3db1b636c07e ("usb:gadget Separated decoding functions from dwc3 driver.")
> >
> > I have used the usb tree from next-20190703 for today.
> >
> > This also occurs in the usb-gadget tree so I have used the version of
> > that from next-20190703 as well.
>
> Odd, I thought I pulled the usb-gadget tree into mine.  Felipe, can you
> take a look at this to see if I messed something up?

This looks like it was caused by Pawel's patches.

I'll try to reproduce here and see what's causing it.

-- 
balbi

  reply	other threads:[~2019-07-04  7:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-04  6:34 linux-next: build failure after merge of the usb and usb-gadget trees Stephen Rothwell
2019-07-04  6:59 ` Greg KH
2019-07-04  7:28   ` Felipe Balbi [this message]
2019-07-04  8:07     ` Pawel Laszczak
2019-07-04  8:25       ` Felipe Balbi
2019-07-04  8:32         ` Greg KH
2019-07-04  8:45           ` Felipe Balbi
2019-07-04 11:03             ` Greg KH
2019-07-04  9:08         ` Pawel Laszczak
2019-07-04  9:25           ` Pawel Laszczak
2019-07-04  9:45             ` Felipe Balbi
2019-07-04  9:44           ` Felipe Balbi
2019-07-04 11:03             ` Greg KH
2019-07-04 11:06               ` Felipe Balbi
2019-07-05  4:42                 ` Pawel Laszczak
2019-07-04 15:53         ` Nishanth Menon
2019-07-08 15:09         ` Sekhar Nori
2019-07-04  7:47   ` 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=CAH8TKc_4ggxOPgii8gLGo2d7nvx08cbTk8_xDUQfA2Ckcxb_Aw@mail.gmail.com \
    --to=balbi@kernel.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=pawell@cadence.com \
    --cc=sfr@canb.auug.org.au \
    /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).