From: Vincent Pelletier <plr.vincent@gmail.com>
To: Felipe Balbi <balbi@kernel.org>
Cc: Randy Dunlap <rdunlap@infradead.org>,
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>,
USB list <linux-usb@vger.kernel.org>
Subject: Re: linux-next: Tree for Dec 14 (usb/dwc3)
Date: Fri, 15 Dec 2017 14:53:32 +0000 [thread overview]
Message-ID: <20171215145325.7c4cd727@gmail.com> (raw)
In-Reply-To: <87wp1ol81e.fsf@linux.intel.com>
Hello,
On Fri, 15 Dec 2017 10:17:17 +0200, Felipe Balbi <balbi@kernel.org>
wrote:
> Randy Dunlap <rdunlap@infradead.org> writes:
> > 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.
>
> please do. write/readl tracepoints haven't changed in ages :-)
Could it be related to this patch ?
https://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git/commit/?h=next&id=204ec1af6257a52fb80f43317f949b345040f9d1
It does touch dwc3_writel & dwc3_readl.
--
Vincent Pelletier
next prev parent reply other threads:[~2017-12-15 14:53 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 ` linux-next: Tree for Dec 14 (usb/dwc3) Randy Dunlap
2017-12-15 8:17 ` Felipe Balbi
2017-12-15 14:53 ` Vincent Pelletier [this message]
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=20171215145325.7c4cd727@gmail.com \
--to=plr.vincent@gmail.com \
--cc=balbi@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.