From: Felipe Balbi <balbi@kernel.org>
To: Greg KH <greg@kroah.com>
Cc: Pawel Laszczak <pawell@cadence.com>,
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>,
"linux-usb\@vger.kernel.org" <linux-usb@vger.kernel.org>,
Roger Quadros <rogerq@ti.com>, Nishanth Menon <nm@ti.com>
Subject: Re: linux-next: build failure after merge of the usb and usb-gadget trees
Date: Thu, 04 Jul 2019 14:06:11 +0300 [thread overview]
Message-ID: <87sgrm9hzw.fsf@linux.intel.com> (raw)
In-Reply-To: <20190704110333.GB1404@kroah.com>
Hi,
Greg KH <greg@kroah.com> writes:
> On Thu, Jul 04, 2019 at 12:44:08PM +0300, Felipe Balbi wrote:
>>
>> Hi,
>>
>> Pawel Laszczak <pawell@cadence.com> writes:
>>
>> >>
>> >>
>> >>Hi,
>> >>
>> >>Pawel Laszczak <pawell@cadence.com> writes:
>> >>
>> >>>>
>> >>>>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.
>> >>>
>> >>> Problem is in my Patch. I reproduced it, but I don't understand why compiler
>> >>> complains about usb_decode_ctrl. It's compiled into libcomposite.ko and
>> >>> declaration is in drivers/usb/gadget.h.
>> >>
>> >>That's because in multi_v7_defconfig dwc3 is built-in while libcomposite
>> >>is a module:
>> >>
>> >>CONFIG_USB_DWC3=y
>> >>CONFIG_USB_LIBCOMPOSITE=m
>> >>
>> >>
>> >>I remember that when you were doing this work, I asked you to move
>> >>functions to usb/common. Why did you deviate from that suggestion? It's
>> >>clear that decoding a ctrl request can be used by peripheral and host
>> >>and we wouldn't have to deal with this problem if you had just followed
>> >>the suggestion.
>> >
>> > Some time ago Greg wrote:
>> > " It's nice to have these in a common place, but you just bloated all of
>> > the USB-enabled systems in the world for the use of 2 odd-ball system
>> > controllers that almost no one has :) "
>> >
>> > So I moved these functions to gadget directory.
>> >
>> > It was mistake that I added debug.c file to libcomposite.ko.
>>
>> The plan is to use this decoding function for xHCI as well. Other host
>> controllers can use it as well.
>>
>> The biggest mistake was to put this under gadget. What you should have
>> done was create a file under usb/common that only gets compile in if
>> tracing is enabled.
>>
>> Then there's no bloating unless you have a kernel purposefuly built for
>> debugging and tracing.
>>
>> Greg, does that work for you?
>
> I guess, but I'd like to see patches before answering that :)
Sure, understandable. I should've done a better job at filtering that
out. Sorry about htat
--
balbi
next prev parent reply other threads:[~2019-07-04 11:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190704163458.63ed69d2@canb.auug.org.au>
[not found] ` <20190704065949.GA32707@kroah.com>
2019-07-04 7:28 ` linux-next: build failure after merge of the usb and usb-gadget trees Felipe Balbi
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 [this message]
2019-07-05 4:42 ` Pawel Laszczak
2019-07-04 15:53 ` Nishanth Menon
2019-07-08 15:09 ` Sekhar Nori
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=87sgrm9hzw.fsf@linux.intel.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=nm@ti.com \
--cc=pawell@cadence.com \
--cc=rogerq@ti.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).