From: Randy Dunlap <rdunlap@infradead.org>
To: 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>,
Felipe Balbi <balbi@kernel.org>
Subject: Re: linux-next: Tree for Dec 14 (usb/dwc3)
Date: Thu, 14 Dec 2017 09:40:19 -0800 [thread overview]
Message-ID: <9d07169a-c00d-e302-f373-f4431899941b@infradead.org> (raw)
In-Reply-To: <20171214180617.5bbff2ec@canb.auug.org.au>
On 12/13/2017 11:06 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20171213:
>
on i386:
ERROR: "__tracepoint_dwc3_writel" [drivers/usb/dwc3/dwc3.ko] undefined!
ERROR: "__tracepoint_dwc3_readl" [drivers/usb/dwc3/dwc3.ko] undefined!
I can send the randconfig file is you need it.
--
~Randy
next prev parent reply other threads:[~2017-12-14 17:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-14 7:06 linux-next: Tree for Dec 14 Stephen Rothwell
2017-12-14 17:40 ` Randy Dunlap [this message]
2017-12-15 8:17 ` linux-next: Tree for Dec 14 (usb/dwc3) Felipe Balbi
2017-12-15 14:53 ` Vincent Pelletier
2017-12-15 19:20 ` 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=9d07169a-c00d-e302-f373-f4431899941b@infradead.org \
--to=rdunlap@infradead.org \
--cc=balbi@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-usb@vger.kernel.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).