linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Linux Crypto List <linux-crypto@vger.kernel.org>,
	Danny Tsen <dtsen@linux.ibm.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: [PATCH] crypto: p10-aes-gcm - Use _GLOBAL instead of .global
Date: Tue, 17 Jan 2023 11:02:27 +1100	[thread overview]
Message-ID: <20230117110227.39fbadcc@canb.auug.org.au> (raw)
In-Reply-To: <Y8UWHwTkKIkQn1t0@gondor.apana.org.au>

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

Hi Herbert,

On Mon, 16 Jan 2023 17:17:19 +0800 Herbert Xu <herbert@gondor.apana.org.au> wrote:
>
> On Mon, Jan 16, 2023 at 11:29:39AM +1100, Stephen Rothwell wrote:
> > 
> > After merging the crypto tree, today's linux-next build (powerpc
> > ppc64_defconfig) failed like this:
> > 
> > ERROR: modpost: ".aes_p10_gcm_decrypt" [arch/powerpc/crypto/p10-aes-gcm-crypto.ko] undefined!
> > ERROR: modpost: ".aes_p10_gcm_encrypt" [arch/powerpc/crypto/p10-aes-gcm-crypto.ko] undefined!
> > 
> > Caused by commits
> > 
> >   cc40379b6e19 ("crypto: p10-aes-gcm - Glue code for AES/GCM stitched implementation")
> >   ca68a96c37eb ("crypto: p10-aes-gcm - An accelerated AES/GCM stitched implementation")  
> 
> Does this patch help?

Yes, that fixes the PowerPC build, thanks.

Tested-by: Stephen Rothwell <sfr@canb.auug.org.au> # build test only

I have added the patch to linux-next for today.
-- 
Cheers,
Stephen Rothwell

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

      reply	other threads:[~2023-01-17  0:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-16  0:29 linux-next: build failure after merge of the crypto tree Stephen Rothwell
2023-01-16  9:17 ` [PATCH] crypto: p10-aes-gcm - Use _GLOBAL instead of .global Herbert Xu
2023-01-17  0:02   ` Stephen Rothwell [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=20230117110227.39fbadcc@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=dtsen@linux.ibm.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.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 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).