From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Robert Schwebel <r.schwebel@pengutronix.de>
Cc: "Marc Kleine-Budde" <mkl@pengutronix.de>,
distrokit@pengutronix.de, "Uwe Kleine-König" <ukl@pengutronix.de>,
"Lucas Stach" <l.stach@pengutronix.de>
Subject: Re: [DistroKit] [PATCH v4] platform-v8a: kernelconfig: cleanup
Date: Mon, 29 Jan 2024 09:38:05 +0100 [thread overview]
Message-ID: <Zbdj7QU-qmUklPyv@pengutronix.de> (raw)
In-Reply-To: <20240127105848.GC176585@pengutronix.de>
Hi,
On Sat, Jan 27, 2024 at 11:58:48AM +0100, Robert Schwebel wrote:
> On Fri, Jan 26, 2024 at 07:40:34PM +0100, Robert Schwebel wrote:
> > Thanks, applied to next.
>
> The testsuite found two issues:
>
> - CONFIG_COMPACTION: You switched this off, but 'reason' claims that it
> should be on, and the help test for the option does also suggest that
> we better enable this. All of our other kernel configs for other
> platforms have it enabled.
Lucas, Marc, I don't remember why we disabled this. Unless you know and
have a good reason, I'd say enable it.
> - CONFIG_CRYPTO_AES is on, CONFIG_CRYPTO_AES_ARM64_CE_CCM is also on,
> but CONFIG_CRYPTO_CCM was switched from m to off.
>
> Was there a specific reason for that, or can we switch both back on?
CONFIG_CRYPTO_CCM is no longer needed by any driver. The correct fix is to
disable CONFIG_CRYPTO_AES_ARM64_CE_CCM instead.
> I have two patches on next that re-enable those options, which might be
> squashed into your patch.
Regards,
Michael
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2024-01-29 8:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 17:04 Michael Olbrich
2024-01-26 18:40 ` Robert Schwebel
2024-01-27 10:58 ` Robert Schwebel
2024-01-29 8:38 ` Michael Olbrich [this message]
2024-01-29 11:38 ` Robert Schwebel
2024-01-29 11:53 ` Lucas Stach
2024-02-01 8:00 ` Michael Olbrich
2024-02-01 8:02 ` Michael Olbrich
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=Zbdj7QU-qmUklPyv@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=distrokit@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=mkl@pengutronix.de \
--cc=r.schwebel@pengutronix.de \
--cc=ukl@pengutronix.de \
/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