From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Lucas Stach <l.stach@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] memedit: fix C23 compatibility
Date: Thu, 15 Jan 2026 16:12:01 +0100 [thread overview]
Message-ID: <20260115151201.230779-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20251214171838.114312-1-l.stach@pengutronix.de>
Thanks, applied as ca4334f2bb8b35079a6f5a4d9e1ec54c333ea6a2.
Michael
[sent from post-receive hook]
On Thu, 15 Jan 2026 16:12:01 +0100, Lucas Stach <l.stach@pengutronix.de> wrote:
> So it can be built with compilers that default to the
> newer C standard.
>
> Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
> Message-Id: <20251214171838.114312-1-l.stach@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/patches/memedit-0.9/0001-use-stdbool.h-instead-of-rolling-our-own.patch b/patches/memedit-0.9/0001-use-stdbool.h-instead-of-rolling-our-own.patch
> new file mode 100644
> index 000000000000..5ba25a6da9ff
> --- /dev/null
> +++ b/patches/memedit-0.9/0001-use-stdbool.h-instead-of-rolling-our-own.patch
> @@ -0,0 +1,36 @@
> +From: Lucas Stach <l.stach@pengutronix.de>
> +Date: Sun, 14 Dec 2025 18:12:57 +0100
> +Subject: [PATCH] use stdbool.h instead of rolling our own
> +
> +With C23 bool is now a proper keyword, so we can not use
> +the check if bool is defined to gate our own fallback.
> +
> +Use stdbool.h instead to have bool types across different
> +compiler versions.
> +
> +Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
> +---
> + memedit_parser.h | 8 +-------
> + 1 file changed, 1 insertion(+), 7 deletions(-)
> +
> +diff --git a/memedit_parser.h b/memedit_parser.h
> +index c5db019b7cde..bed7544a789e 100644
> +--- a/memedit_parser.h
> ++++ b/memedit_parser.h
> +@@ -14,15 +14,9 @@
> + **
> + ******************************************************************************/
> +
> ++#include <stdbool.h>
> + #include <stdio.h>
> +
> +-#ifndef bool
> +-typedef enum bool_t
> +-{
> +- false = 0, true
> +-} bool;
> +-#endif
> +-
> + /* customized structure for command line parameters */
> + struct arg_t
> + {
> diff --git a/patches/memedit-0.9/series b/patches/memedit-0.9/series
> new file mode 100644
> index 000000000000..4c98424f3381
> --- /dev/null
> +++ b/patches/memedit-0.9/series
> @@ -0,0 +1,4 @@
> +# generated by git-ptx-patches
> +#tag:base --start-number 1
> +0001-use-stdbool.h-instead-of-rolling-our-own.patch
> +# 84c619bd32bb289e17dd64b996d9ffb8 - git-ptx-patches magic
prev parent reply other threads:[~2026-01-15 15:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-14 17:18 [ptxdist] [PATCH] " Lucas Stach
2026-01-15 15:12 ` Michael Olbrich [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=20260115151201.230779-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=ptxdist@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