All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Chancellor <natechancellor@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Jackie Liu <liuyun01@kylinos.cn>,
	Nick Desaulniers <ndesaulniers@google.com>,
	Will Deacon <will.deacon@arm.com>,
	Stephen Hines <srhines@google.com>,
	Kevin Hilman <khilman@baylibre.com>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm64: crypto: Disable xor-neon build when using clang
Date: Thu, 14 Feb 2019 10:00:32 -0700	[thread overview]
Message-ID: <20190214170032.GA30494@archlinux-ryzen> (raw)
In-Reply-To: <20190214163047.GC11988@sirena.org.uk>

On Thu, Feb 14, 2019 at 04:30:48PM +0000, Mark Brown wrote:
> On Wed, Feb 13, 2019 at 01:45:08PM -0800, Nick Desaulniers wrote:
> 
> > Nathan's patch [0] is probably ready to go; with Ard's suggested by
> > tag [1].  Again, I'm not happy about it; but KernelCI coverage is
> > ultimately more important to the project.
> 
> OK, Nathan will you post that?

Yes, I can do it later today.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2019-02-14 17:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-12 19:46 [PATCH] arm64: crypto: Disable xor-neon build when using clang Mark Brown
2019-02-12 20:33 ` Ard Biesheuvel
2019-02-13 11:40   ` Mark Brown
2019-02-13 21:45     ` Nick Desaulniers
2019-02-14 16:30       ` Mark Brown
2019-02-14 17:00         ` Nathan Chancellor [this message]

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=20190214170032.GA30494@archlinux-ryzen \
    --to=natechancellor@gmail.com \
    --cc=ard.biesheuvel@linaro.org \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=khilman@baylibre.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=liuyun01@kylinos.cn \
    --cc=ndesaulniers@google.com \
    --cc=srhines@google.com \
    --cc=will.deacon@arm.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 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.