linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vlad Dronov <vdronov@redhat.com>
To: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, LKML <linux-kernel@vger.kernel.org>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	Harald Freudenberger <freude@linux.ibm.com>
Subject: Re: include/crypto/chacha.h:100: undefined reference to `chacha_crypt_arch'
Date: Mon, 4 Jul 2022 21:22:53 +0200	[thread overview]
Message-ID: <CAMusb+QqSU0ak2Dd2pqWcS82u9z5iTyqHp7CQZNuDCm5Juhrxw@mail.gmail.com> (raw)
In-Reply-To: <CAMusb+Rr9_TBLad1UQN52nWBN48j8V1c8GmMPNz=ezsEZfGKOg@mail.gmail.com>

Hi,

On Mon, Jul 4, 2022 at 5:42 PM Vlad Dronov <vdronov@redhat.com> wrote:
> ...skip...
>
> JFYI: fed with a config in question, "make menuconfig" just silently changes
> CONFIG_CRYPTO_CHACHA_S390=m to =y
> and, accordingly,
> CONFIG_CRYPTO_ARCH_HAVE_LIB_CHACHA=m to =y
> thus allowing a correct build.
>
> Still not sure how to proceed from here with this clarification above.

Ok, I'm sorry for the traffic. The fix was posted:

https://lore.kernel.org/netdev/20220704191535.76006-1-vdronov@redhat.com/T/#u

Best regards,
Vladis Dronov | Red Hat, Inc. | The Core Kernel | Senior Software Engineer


      reply	other threads:[~2022-07-04 19:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-02 22:49 include/crypto/chacha.h:100: undefined reference to `chacha_crypt_arch' kernel test robot
2022-07-04 14:35 ` Vlad Dronov
2022-07-04 14:58   ` Vlad Dronov
2022-07-04 15:24     ` Vlad Dronov
2022-07-04 15:42       ` Vlad Dronov
2022-07-04 19:22         ` Vlad Dronov [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=CAMusb+QqSU0ak2Dd2pqWcS82u9z5iTyqHp7CQZNuDCm5Juhrxw@mail.gmail.com \
    --to=vdronov@redhat.com \
    --cc=freude@linux.ibm.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.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;
as well as URLs for NNTP newsgroup(s).