From: Sascha Hauer <s.hauer@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: Jonas Rebmann <jre@pengutronix.de>,
	BAREBOX <barebox@lists.infradead.org>
Subject: Re: [PATCH v2 17/17] Documentation: migration-2025.11.0: List changes to CONFIG_CRYPTO_PUBLIC_KEYS
Date: Mon, 3 Nov 2025 11:41:16 +0100	[thread overview]
Message-ID: <aQiGzCPQkg70Q_Wx@pengutronix.de> (raw)
In-Reply-To: <9bcaaf69-142e-446a-a30d-ba538e62097a@pengutronix.de>
On Mon, Nov 03, 2025 at 11:26:34AM +0100, Ahmad Fatoum wrote:
> 
> 
> On 11/3/25 11:16 AM, Sascha Hauer wrote:
> > On Tue, Oct 28, 2025 at 07:03:22PM +0100, Jonas Rebmann wrote:
> >> As part of the introduction of TLV signature in public key keyrings,
> >> there is a new interpreter for CONFIG_CRYPTO_PUBLIC_KEYS in
> >> scripts/keytoc.c. All users should update to the new syntax and are
> >> presented with a warning. Users with invalid characters in the legacy
> >> syntax must change the fit-hint and will be presented with an error.
> >>
> >> Signed-off-by: Jonas Rebmann <jre@pengutronix.de>
> >> ---
> >>  Documentation/migration-guides/migration-2025.11.0.rst | 15 +++++++++++++++
> >>  1 file changed, 15 insertions(+)
> >>
> >> diff --git a/Documentation/migration-guides/migration-2025.11.0.rst b/Documentation/migration-guides/migration-2025.11.0.rst
> >> index a9c7abb66e..bd7fcf8126 100644
> >> --- a/Documentation/migration-guides/migration-2025.11.0.rst
> >> +++ b/Documentation/migration-guides/migration-2025.11.0.rst
> > 
> > migration-2025.12.0.rst please.
> 
> Should we rethink the scheme to avoid this in future?
Yes. The contributor shouldn't need to know which release a series
targets and also not have to remember to move it to another migration
guide when sending a new revision after a release.
> 
> Two suggestions come to mind:
> 
> - We add migration-next.rst and migration-master.rst files, where stuff
> can be added and then they are renamed before release:
> 
> migration-master.rst -> migration-${version}.rst
> migration-next.rst -> migration-master.rst
> <empty file> -> migration-next.rst
No need to split this up into migration-master.rst and
migration-next.rst. Let's just use migration.rst. I'll rename
that to migration-20xx.yy right before a release.
Sascha
-- 
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:[~2025-11-03 10:41 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-28 18:03 [PATCH v2 00/17] TLV-Signature and keyrings Jonas Rebmann
2025-10-28 18:03 ` [PATCH v2 01/17] lib: idr: avoid dangling else in idr_for_each_entry() Jonas Rebmann
2025-11-03 10:11   ` Ahmad Fatoum
2025-10-28 18:03 ` [PATCH v2 02/17] common: clean up TLV code Jonas Rebmann
2025-10-28 18:03 ` [PATCH v2 03/17] crypto: Add support for keyrings Jonas Rebmann
2025-10-28 18:03 ` [PATCH v2 04/17] fit: only accept keys from "fit"-keyring Jonas Rebmann
2025-11-03  9:04   ` Sascha Hauer
2025-10-28 18:03 ` [PATCH v2 05/17] crypto: keytoc: Rename "hint" to "fit-hint" and do not use it in identifiers Jonas Rebmann
2025-10-28 18:03 ` [PATCH v2 06/17] commands: keys: update output format to include keyring Jonas Rebmann
2025-10-28 18:03 ` [PATCH v2 07/17] commands: tlv: Error out on invalid TLVs Jonas Rebmann
2025-10-28 18:03 ` [PATCH v2 08/17] scripts: bareboxtlv-generator: Implement signature Jonas Rebmann
2025-10-28 18:03 ` [PATCH v2 09/17] scripts: bareboxtlv-generator: Increase max_size in example schema Jonas Rebmann
2025-10-28 18:03 ` [PATCH v2 10/17] common: tlv: Add TLV-Signature support Jonas Rebmann
2025-11-03 10:02   ` Sascha Hauer
2025-11-03 11:21     ` Jonas Rebmann
2025-11-03 11:41       ` Sascha Hauer
2025-11-03 11:55         ` Jonas Rebmann
2025-10-28 18:03 ` [PATCH v2 11/17] common: tlv: default decoder for signed TLV Jonas Rebmann
2025-10-28 18:03 ` [PATCH v2 12/17] crypto: Use "development" keys for "fit" and "tlv" keyring Jonas Rebmann
2025-10-28 18:03 ` [PATCH v2 13/17] test: py: add signature to TLV integration tests Jonas Rebmann
2025-10-28 18:03 ` [PATCH v2 14/17] ci: pytest: Add kconfig fragment for TLV signature " Jonas Rebmann
2025-10-28 18:03 ` [PATCH v2 15/17] crypto: concatenate fit development certificate with private key Jonas Rebmann
2025-11-03 10:08   ` Sascha Hauer
2025-11-03 11:41     ` Jonas Rebmann
2025-10-28 18:03 ` [PATCH v2 16/17] doc/barebox-tlv: Update documentation regarding TLV-Signature Jonas Rebmann
2025-10-28 18:03 ` [PATCH v2 17/17] Documentation: migration-2025.11.0: List changes to CONFIG_CRYPTO_PUBLIC_KEYS Jonas Rebmann
2025-11-03 10:16   ` Sascha Hauer
2025-11-03 10:26     ` Ahmad Fatoum
2025-11-03 10:41       ` Sascha Hauer [this message]
2025-11-03 10:45         ` Ahmad Fatoum
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=aQiGzCPQkg70Q_Wx@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=jre@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