From: Petr Vorel <petr.vorel@gmail.com>
To: Edgar Bonet <bonet@grenoble.cnrs.fr>
Cc: Kanak Shilledar <kanak.shilledar@axis.com>,
buildroot@buildroot.org, Edgar Bonet <bonet@grenoble.cnrs.fr>,
Arnout Vandecappelle <arnout@mind.be>,
Titouan Christophe <titouan.christophe@mind.be>
Subject: Re: [Buildroot] [RESEND v3 1/1] support: kconfig: Fix compiler warnings
Date: Tue, 12 May 2026 23:16:47 +0200 [thread overview]
Message-ID: <20260512211647.GA67744@pevik> (raw)
In-Reply-To: <1d003106-63b6-49d5-90c0-4f7c0f2f1f79@grenoble.cnrs.fr>
Hi all,
[ Cc Edgar and Arnout involved in 324612d68e and Titouan working on kconfig
update ]
@Kanak I'm sorry, reading the description of the failure:
324612d68e ("support/kconfig: fix compiler warnings")
Normally, we want changes to kconfig to be reflected by patches in
support/kconfig/patches. This makes it easier to resync with upstream
kconfig. However, in this case, everything that is changed here is
already changed completely (and differently) upstream, so there is no
added value in keeping the patch.
That means I was wrong in v1 where I asked for creating a patch.
OTOH it's a bit confusing, it should be at least documented in
support/kconfig/README.buildroot.
> Hello Buildroot people!
> On 2026-05-12, Kanak Shilledar wrote:
> > Add a new patch to fix the compiler warning given on Ubuntu 24.04.4 in
> > `util.c` warning of `-Wformat-overflow=`. [...]
> This seems to me like a duplicate of a patch[1] I sent in July 2025, as
> part of a series[2] that also updated support/kconfig/patches/.
Thanks, for pointing this out. Indeed it is. I'm sorry that I haven't finished
the review. Unfortunately nobody else haven't reviewed it [4] [5] (state new in
patchwork for one year old patch is not good).
> Also, both your patch and my series are likely in conflict with a more
> comprehensive rework of kconfig[3] proposed by Titouan Christophe on
> 2026-02-04.
[6] [7]
Thanks for the reminder. I'd actually prefer to have this update. There is some
requirement to change it but that should be trivial to fix in new version.
@Titouan do you plan to send a new version?
Kind regards,
Petr
> Regards,
> Edgar Bonet.
> [1] https://lists.buildroot.org/pipermail/buildroot/2025-July/782825.html
> [2] https://lists.buildroot.org/pipermail/buildroot/2025-July/782822.html
> [3] https://lists.buildroot.org/pipermail/buildroot/2026-February/796328.html
[4] https://patchwork.ozlabs.org/project/buildroot/list/?series=465475&state=*
[5] https://lore.kernel.org/buildroot/c8467198-efc1-45f9-86ef-0726d06df295@grenoble.cnrs.fr/#r
[6] https://patchwork.ozlabs.org/project/buildroot/list/?series=490997&state=*
[7] https://lore.kernel.org/buildroot/20260204154340.766528-1-titouan.christophe@mind.be/#r
[8] https://lore.kernel.org/buildroot/20260205082847.4b855528@pc-1/
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-05-12 21:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 10:56 [Buildroot] [RESEND v3 0/1] support: kconfig: Fix compiler warnings Kanak Shilledar
2026-05-12 10:56 ` [Buildroot] [RESEND v3 1/1] " Kanak Shilledar
2026-05-12 13:36 ` Edgar Bonet via buildroot
2026-05-12 21:16 ` Petr Vorel [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=20260512211647.GA67744@pevik \
--to=petr.vorel@gmail.com \
--cc=arnout@mind.be \
--cc=bonet@grenoble.cnrs.fr \
--cc=buildroot@buildroot.org \
--cc=kanak.shilledar@axis.com \
--cc=titouan.christophe@mind.be \
/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