linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
To: Randy Dunlap <rdunlap@infradead.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux-Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	USB list <linux-usb@vger.kernel.org>
Subject: RE: linux-next: Tree for Aug 31 (drivers/usb/gadget/udc/renesas_usb3)
Date: Mon, 3 Sep 2018 03:20:23 +0000	[thread overview]
Message-ID: <OSBPR01MB2293786602584B7F92A4A333D80C0@OSBPR01MB2293.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <d3eaa71e-c11d-82c7-27c3-3cd0a2b031c2@infradead.org>

Hi,

> From: Randy Dunlap, Sent: Saturday, September 1, 2018 12:43 AM
> 
> On 08/30/2018 08:03 PM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20180830:
> >
> 
> on i386:
> 
> drivers/usb/gadget/udc/renesas_usb3.o: In function `renesas_usb3_probe':
> renesas_usb3.c:(.text+0x16da): undefined reference to `usb_of_get_companion_dev'
> 
> 
> Full randconfig file is attached.

Thank you for the report!
I already submitted a fix patch [1]. But this patch is not applied yet.

[1]
https://marc.info/?l=linux-usb&m=153476263226681&w=2


Related ML archives:
https://marc.info/?l=linux-usb&m=153382696712253&w=2
https://marc.info/?l=linux-usb&m=153419699328537&w=2

Best regards,
Yoshihiro Shimoda


> --
> ~Randy

  reply	other threads:[~2018-09-03  3:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-31  3:03 linux-next: Tree for Aug 31 Stephen Rothwell
2018-08-31 15:43 ` linux-next: Tree for Aug 31 (drivers/usb/gadget/udc/renesas_usb3) Randy Dunlap
2018-09-03  3:20   ` Yoshihiro Shimoda [this message]
2018-08-31 15:57 ` linux-next: Tree for Aug 31 (nixge.c and phy) Randy Dunlap
2018-08-31 16:36   ` Moritz Fischer
2018-08-31 17:54     ` Andrew Lunn
2018-08-31 17:52       ` Moritz Fischer
2018-08-31 18:19         ` Andrew Lunn
2018-08-31 16:14 ` linux-next: Tree for Aug 31 (mix of ethernet and phy build errors) Randy Dunlap

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=OSBPR01MB2293786602584B7F92A4A333D80C0@OSBPR01MB2293.jpnprd01.prod.outlook.com \
    --to=yoshihiro.shimoda.uh@renesas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --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).