Messages in this thread | | | Subject | Re: [PATCH v2 6/6] KEYS: trusted: Introduce support for NXP CAAM-based trusted keys | From | Ahmad Fatoum <> | Date | Wed, 21 Jul 2021 19:02:38 +0200 |
| |
Hi,
On 20.07.21 21:19, Richard Weinberger wrote: > On Fri, Jul 2, 2021 at 2:37 PM Ahmad Fatoum <a.fatoum@pengutronix.de> wrote: >>> Both is possible. If the string starts with "0x" it needs to be decoded to a >>> 128 bit key. Otherwise it has to be a up to 16 byte string. >> >> Fine by me. Looking forward to your patches. :-) > > I'm not sure how to proceed. Should I base my changes on this series > or do you plan to send an updated > version soon? > Maybe it makes also sense to base my DCP patch set on yours. > > Trusted Keys maintainers, what do you prefer?
I sent out v3 despite the name (of course forgot that git-send-email -vX is silently dropped when sending patch files directly..):
https://lore.kernel.org/linux-integrity/cover.9fc9298fd9d63553491871d043a18affc2dbc8a8.1626885907.git-series.a.fatoum@pengutronix.de/T/#t
I'd advise you base your changes on the first two patches there as well as the Kconfig fix/enhancement I sent out separately: https://lore.kernel.org/linux-integrity/20210721160258.7024-1-a.fatoum@pengutronix.de/T/#u
Those are relevant for you as well and I assume they should be good to be merged even if the CAAM series turns out to need some more love.
Cheers, Ahmad
-- 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 |
| |