From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Felipe Balbi <balbi@kernel.org>, linux-usb@vger.kernel.org
Cc: Greg KH <greg@kroah.com>, Joel Stanley <joel@jms.id.au>,
Andrew Jeffery <andrew@aj.id.au>
Subject: [v7] usb/gadget: Add driver for Aspeed SoC virtual hub
Date: Thu, 29 Mar 2018 10:10:02 +1100 [thread overview]
Message-ID: <1522278602.21446.52.camel@kernel.crashing.org> (raw)
On Thu, 2018-03-29 at 09:26 +1100, Benjamin Herrenschmidt wrote:
> On Thu, 2018-03-29 at 09:19 +1100, Benjamin Herrenschmidt wrote:
> > On Tue, 2018-03-27 at 10:30 +0300, Felipe Balbi wrote:
> > > $ gcc --version
> > > gcc (Debian 7.3.0-12) 7.3.0
> >
> > BTW. What debian version while at it ?
> >
> > I still haven't managed to find a gcc that reproduces this, so I
> > probably need to get the exact same distro you are using installed
> > somewhere :-(
>
> Can you also send me your .config in case there are specific options in
> there that enable extra checking that I've missed ?
Ignore me, I found it !
You need to compile for x86, which then makes CONFIG_FORTIFY_SOURCE,
which then needs to be turned on, then I can hit it with 7.3.1 in
Fedora.
I'll work with the gcc guys to figure out what's up.
Cheers,
Ben.
---
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2018-03-28 23:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 23:10 Benjamin Herrenschmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-03-28 22:26 [v7] usb/gadget: Add driver for Aspeed SoC virtual hub Benjamin Herrenschmidt
2018-03-28 22:19 Benjamin Herrenschmidt
2018-03-27 7:57 Benjamin Herrenschmidt
2018-03-27 7:30 Felipe Balbi
2018-03-26 0:32 Benjamin Herrenschmidt
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=1522278602.21446.52.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=andrew@aj.id.au \
--cc=balbi@kernel.org \
--cc=greg@kroah.com \
--cc=joel@jms.id.au \
--cc=linux-usb@vger.kernel.org \
/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).