From: schwab@suse.de (Andreas Schwab)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64/crypto: fix makefile rule for aes-glue-%.o
Date: Mon, 30 Jun 2014 15:56:50 +0200 [thread overview]
Message-ID: <mvmr4264i1p.fsf@hawking.suse.de> (raw)
In-Reply-To: <CAKv+Gu-NAVjMR-Jkw=W-8f7M5FSsQOSdzYN6A0kHDd1m0WA8EA@mail.gmail.com> (Ard Biesheuvel's message of "Mon, 30 Jun 2014 15:38:41 +0200")
Ard Biesheuvel <ard.biesheuvel@linaro.org> writes:
> Out of curiosity, how did you trigger this failure? I have build this
> code numerous times (and so have others) and I have never seen this
> failure.
Did you ever start with a clean tree?
Andreas.
--
Andreas Schwab, SUSE Labs, schwab at suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
WARNING: multiple messages have this Message-ID (diff)
From: Andreas Schwab <schwab@suse.de>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: "linux-arm-kernel\@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64/crypto: fix makefile rule for aes-glue-%.o
Date: Mon, 30 Jun 2014 15:56:50 +0200 [thread overview]
Message-ID: <mvmr4264i1p.fsf@hawking.suse.de> (raw)
In-Reply-To: <CAKv+Gu-NAVjMR-Jkw=W-8f7M5FSsQOSdzYN6A0kHDd1m0WA8EA@mail.gmail.com> (Ard Biesheuvel's message of "Mon, 30 Jun 2014 15:38:41 +0200")
Ard Biesheuvel <ard.biesheuvel@linaro.org> writes:
> Out of curiosity, how did you trigger this failure? I have build this
> code numerous times (and so have others) and I have never seen this
> failure.
Did you ever start with a clean tree?
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2014-06-30 13:56 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 13:14 [PATCH] arm64/crypto: fix makefile rule for aes-glue-%.o Andreas Schwab
2014-06-30 13:14 ` Andreas Schwab
2014-06-30 13:38 ` Ard Biesheuvel
2014-06-30 13:38 ` Ard Biesheuvel
2014-06-30 13:56 ` Andreas Schwab [this message]
2014-06-30 13:56 ` Andreas Schwab
2014-06-30 14:08 ` Ard Biesheuvel
2014-06-30 14:08 ` Ard Biesheuvel
2014-07-24 12:29 ` Andreas Schwab
2014-07-24 12:29 ` Andreas Schwab
2014-07-24 12:35 ` Ard Biesheuvel
2014-07-24 12:35 ` Ard Biesheuvel
2014-07-24 12:53 ` Ard Biesheuvel
2014-07-24 12:53 ` Ard Biesheuvel
2014-07-24 13:26 ` Andreas Schwab
2014-07-24 13:26 ` Andreas Schwab
2014-07-24 13:29 ` Ard Biesheuvel
2014-07-24 13:29 ` Ard Biesheuvel
2014-07-24 13:40 ` Andreas Schwab
2014-07-24 13:40 ` Andreas Schwab
2014-07-24 14:18 ` Ard Biesheuvel
2014-07-24 14:18 ` Ard Biesheuvel
2014-07-24 14:24 ` Ard Biesheuvel
2014-07-24 14:24 ` Ard Biesheuvel
2014-07-24 16:12 ` Sam Ravnborg
2014-07-24 16:12 ` Sam Ravnborg
2014-07-24 19:25 ` Ard Biesheuvel
2014-07-24 19:25 ` Ard Biesheuvel
2014-07-24 20:45 ` Sam Ravnborg
2014-07-24 20:45 ` Sam Ravnborg
2014-07-25 6:28 ` Ard Biesheuvel
2014-07-25 6:28 ` Ard Biesheuvel
2014-07-27 18:40 ` Sam Ravnborg
2014-07-27 18:40 ` Sam Ravnborg
2014-07-28 17:00 ` Ard Biesheuvel
2014-07-28 17:00 ` Ard Biesheuvel
2014-07-28 19:06 ` Sam Ravnborg
2014-07-28 19:06 ` Sam Ravnborg
-- strict thread matches above, loose matches on Subject: below --
2014-07-24 16:03 Ard Biesheuvel
2014-07-24 16:47 ` Catalin Marinas
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=mvmr4264i1p.fsf@hawking.suse.de \
--to=schwab@suse.de \
--cc=linux-arm-kernel@lists.infradead.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 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.