From: Herbert Xu <herbert@gondor•apana.org.au>
To: Andy Shevchenko <andy.shevchenko@gmail•com>
Cc: Jim Davis <jim.epost@gmail•com>,
Stephen Rothwell <sfr@canb•auug.org.au>,
linux-next <linux-next@vger•kernel.org>,
linux-kernel <linux-kernel@vger•kernel.org>,
"David S. Miller" <davem@davemloft•net>,
linux-crypto <linux-crypto@vger•kernel.org>,
Waiman Long <Waiman.Long@hp•com>,
"Peter Zijlstra (Intel)" <peterz@infradead•org>,
Ingo Molnar <mingo@kernel•org>, "x86@kernel•org" <x86@kernel•org>
Subject: Re: randconfig build error with next-20150529, in crypto/jitterentropy.c
Date: Mon, 8 Jun 2015 20:25:02 +0800 [thread overview]
Message-ID: <20150608122502.GA29454@gondor.apana.org.au> (raw)
In-Reply-To: <CAHp75VeoCQSUCeswTCzUyKbV_e4RTt5t0yjEJLSzAvtX8jFvNw@mail.gmail.com>
On Mon, Jun 08, 2015 at 03:21:09PM +0300, Andy Shevchenko wrote:
> On Fri, May 29, 2015 at 10:14 PM, Jim Davis <jim.epost@gmail•com> wrote:
> > Building with the attached random configuration file,
>
> Hit the very same error against next-20150605.
>
> The issue with that file we have no compiler optimization enabled. So,
> guys, how you would recommend to fix it?
Stephan, can we get rid of the no optimisation requirement?
Thanks,
--
Email: Herbert Xu <herbert@gondor•apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2015-06-08 12:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 19:14 randconfig build error with next-20150529, in crypto/jitterentropy.c Jim Davis
2015-06-08 12:21 ` Andy Shevchenko
2015-06-08 12:25 ` Herbert Xu [this message]
2015-06-08 12:36 ` Peter Zijlstra
2015-06-08 12:44 ` Stephan Mueller
2015-06-08 15:52 ` Stephan Mueller
2015-06-08 15:59 ` Peter Zijlstra
2015-06-08 19:54 ` Guenter Roeck
2015-06-08 22:36 ` Stephan Mueller
2015-06-08 23:30 ` Guenter Roeck
2015-06-08 23:33 ` Stephan Mueller
2015-06-08 23:51 ` Guenter Roeck
2015-06-09 0:10 ` Stephan Mueller
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=20150608122502.GA29454@gondor.apana.org.au \
--to=herbert@gondor$(echo .)apana.org.au \
--cc=Waiman.Long@hp$(echo .)com \
--cc=andy.shevchenko@gmail$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=jim.epost@gmail$(echo .)com \
--cc=linux-crypto@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mingo@kernel$(echo .)org \
--cc=peterz@infradead$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=x86@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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