public inbox for linux-crypto@vger.kernel.org
 help / color / mirror / Atom feed
From: Herbert Xu <herbert@gondor.apana.org.au>
To: Denis Kenzior <denkenz@gmail.com>
Cc: Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
	Marcel Holtmann <marcel@holtmann.org>,
	James Prestwood <prestwoj@gmail.com>
Subject: Re: Linux 6.5 broke iwd
Date: Thu, 12 Oct 2023 10:26:55 +0800	[thread overview]
Message-ID: <ZSdZb8DVm6e0ikwx@gondor.apana.org.au> (raw)
In-Reply-To: <4f5f4d52-a1c4-4726-80c2-dcc8b3e86e5c@gmail.com>

On Wed, Oct 11, 2023 at 09:18:04PM -0500, Denis Kenzior wrote:
> 
> Possible.  I performed the bisect using a kernel configuration from the
> following instructions:
> 
> https://git.kernel.org/pub/scm/network/wireless/iwd.git/tree/doc/test-runner.txt#n55
> 
> In my case, I was using the User Mode Linux arch and testing locally using
> iwd's test runner.
> 
> # make ARCH=um olddefconfig
> # make ARCH=um -j8

I can't reproduce this with olddefconfig.  It produces a config
where crypto/asymmetric_keys is disabled altogether.

Please send me your actual config file that triggers the build
failure.

Thanks,
-- 
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

  reply	other threads:[~2023-10-12  2:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-11 17:11 Linux 6.5 broke iwd Denis Kenzior
2023-10-12  0:38 ` Herbert Xu
2023-10-12  2:18   ` Denis Kenzior
2023-10-12  2:26     ` Herbert Xu [this message]
2023-10-12  2:33   ` Herbert Xu
2023-10-12  3:09     ` Denis Kenzior
2023-10-12  3:28       ` Herbert Xu
2023-10-12 14:19         ` Denis Kenzior
2023-10-12 14:28           ` Herbert Xu
2023-10-12 15:08             ` Denis Kenzior
2023-10-16  8:35               ` [PATCH] KEYS: asymmetric: Fix sign/verify on pkcs1pad without a hash Herbert Xu
2023-10-16 19:37                 ` Denis Kenzior

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=ZSdZb8DVm6e0ikwx@gondor.apana.org.au \
    --to=herbert@gondor.apana.org.au \
    --cc=denkenz@gmail.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=prestwoj@gmail.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