From: Michael Ellerman <mpe@ellerman.id.au>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-next@vger.kernel.org
Subject: Re: [PATCH] crypto: api - Export crypto_boot_test_finished
Date: Mon, 25 Oct 2021 17:28:24 +1100 [thread overview]
Message-ID: <87sfwpbotz.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <20210928151621.7aec3f34@canb.auug.org.au>
Stephen Rothwell <sfr@canb.auug.org.au> writes:
> Hi Herbert,
>
> On Mon, 27 Sep 2021 19:23:42 +0800 Herbert Xu <herbert@gondor.apana.org.au> wrote:
>>
>> Oops, does this patch fix the problem?
>
> Yes, that fixes my build, thanks.
>
> Tested-by: Stephen Rothwell <sfr@canb.auug.org.au> # ppc32 build
It fixes the build, but modules_install still fails:
$ git checkout adad556efcdd42a1d9e060cbe5f6161cccf1fa28
HEAD is now at adad556efcdd crypto: api - Fix built-in testing dependency failures
$ git show e42dff467ee6 | patch -p1 # apply fixup patch
patching file crypto/api.c
$ make -s -j $(nproc) modules
$ make -s modules_install
depmod: ERROR: Cycle detected: crypto -> crypto_algapi -> crypto
depmod: ERROR: Found 2 modules in dependency cycles!
make: *** [Makefile:1801: modules_install] Error 1
cheers
next prev parent reply other threads:[~2021-10-25 6:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 4:32 linux-next: build failure after merge of the crypto tree Stephen Rothwell
2021-09-27 11:23 ` [PATCH] crypto: api - Export crypto_boot_test_finished Herbert Xu
2021-09-28 5:16 ` Stephen Rothwell
2021-10-25 6:28 ` Michael Ellerman [this message]
2021-10-26 4:38 ` Herbert Xu
2021-10-29 6:09 ` Michael Ellerman
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=87sfwpbotz.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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