public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-s390 <linux-s390@vger.kernel.org>,
	Harald Freudenberger <freude@linux.ibm.com>,
	Patrick Steuer <steuer@linux.ibm.com>,
	Ondrej Mosnacek <omosnace@redhat.com>
Subject: Re: linux-next: Tree for Jul 31 - s390 crypto build breakage
Date: Fri, 2 Aug 2019 14:48:44 +1000	[thread overview]
Message-ID: <20190802144844.43508be1@canb.auug.org.au> (raw)
In-Reply-To: <20190802031414.GB14879@gondor.apana.org.au>

[-- Attachment #1: Type: text/plain, Size: 438 bytes --]

Hi Herbert,

On Fri, 2 Aug 2019 13:14:14 +1000 Herbert Xu <herbert@gondor.apana.org.au> wrote:
>
> For now I'm going to back out those two specific patches as the
> rest seem to be valid by themselves.

I have applied the top commit from your tree to linux-next today just
to help with building and testing over the weekend (I had already
merged your tree before you added the revert).

Thanks
-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2019-08-02  4:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190731163915.3fdfcb14@canb.auug.org.au>
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
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 [this message]
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=20190802144844.43508be1@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=ard.biesheuvel@linaro.org \
    --cc=freude@linux.ibm.com \
    --cc=heiko.carstens@de.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=omosnace@redhat.com \
    --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