From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-s390@vger.kernel.org,
Harald Freudenberger <freude@linux.ibm.com>,
Patrick Steuer <steuer@linux.ibm.com>
Subject: Re: linux-next: Tree for Jul 31 - s390 crypto build breakage
Date: Wed, 31 Jul 2019 13:15:20 +0200 [thread overview]
Message-ID: <20190731111520.GC3488@osiris> (raw)
In-Reply-To: <20190731110816.GA20753@gondor.apana.org.au>
On Wed, Jul 31, 2019 at 09:08:17PM +1000, Herbert Xu wrote:
> On Wed, Jul 31, 2019 at 10:58:20AM +0200, Heiko Carstens wrote:
> > On Wed, Jul 31, 2019 at 04:39:15PM +1000, Stephen Rothwell wrote:
> > > Hi all,
> > >
> > > Changes since 20190730:
> >
> > Hello Ard,
> >
> > two of your patches in the crypto tree cause build breakage on s390:
> >
> > The patch ("crypto: aes - create AES library based on the fixed time AES code")
> > causes this:
>
> Ard already sent a patch for this which I've just pushed out.
Ok, thanks!
However that doesn't fix the simd.h header file breakage with the
second patch :)
next prev parent reply other threads:[~2019-07-31 11:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 6:39 linux-next: Tree for Jul 31 Stephen Rothwell
2019-07-31 8:58 ` linux-next: Tree for Jul 31 - s390 crypto build breakage Heiko Carstens
2019-07-31 11:08 ` Herbert Xu
2019-07-31 11:15 ` Heiko Carstens [this message]
2019-07-31 11:32 ` Herbert Xu
2019-07-31 11:44 ` Heiko Carstens
2019-08-01 12:28 ` Heiko Carstens
2019-08-01 17:28 ` Ard Biesheuvel
2019-08-02 0:20 ` Stephen Rothwell
2019-08-02 3:14 ` Herbert Xu
2019-08-02 4:48 ` Stephen Rothwell
2019-08-02 6:49 ` Heiko Carstens
2019-08-02 6:44 ` Ard Biesheuvel
2019-08-02 6:50 ` Herbert Xu
2019-08-02 6:47 ` Ard Biesheuvel
2019-08-02 6:46 ` Heiko Carstens
2019-08-02 6:49 ` Ard Biesheuvel
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=20190731111520.GC3488@osiris \
--to=heiko.carstens@de.ibm.com \
--cc=ard.biesheuvel@linaro.org \
--cc=freude@linux.ibm.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=steuer@linux.ibm.com \
/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).