From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Andreas Ziegler <br025@umbiko.net>
Cc: Alexander Sverdlin <alexander.sverdlin@gmail.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2] boot/syslinux: Bump to 6.04-pre2
Date: Thu, 29 Oct 2026 21:30:13 +0100 [thread overview]
Message-ID: <auOsS9x90TIovctY@windsurf> (raw)
In-Reply-To: <ec78e4b982b6b8b0a3ccc04fc9b70ca5@umbiko.net>
On Wed, Oct 28, 2026 at 04:48:51AM +0000, Andreas Ziegler wrote:
> On 2026-10-27 08:19, Thomas Petazzoni wrote:
> > On Tue, Oct 27, 2026 at 04:54:45AM +0000, Andreas Ziegler wrote:
> >
> > > Yes, there is still interest in this software, and I sadly mourn the
> > > absence
> > > of the don't-delete-host-syslinux patch.
> >
> > Not sure to understand this one. Could you clarify? Is Alexander's
> > patch dropping some feature that exists today in boot/syslinux/ and
> > that is important for you?
>
> The v1 of this patch was a series, which contained one additional patch: https://patchwork.buildroot.org/project/buildroot/patch/20260830181907.106154-2-alexander.sverdlin@gmail.com/
> . This unfortunately did not meet the upstream requirement. This change
> would make a messy (and dangerous) installation of syslinux on the build
> machine obsolete.
Which change? Your proposed change at
https://patchwork.buildroot.org/project/buildroot/patch/20260830181907.106154-2-alexander.sverdlin@gmail.com/
? Sorry, I'm still not following you. Could you perhaps bring a bit
more context?
> Last time I did low-level C and assembler programming was during university,
> which is now more than 30 years in the past -- but if it helps keeping
> syslinux active, why not.
All we care is about keeping syslinux active: reacting to build
issues, to new upstream releases, to patches being submitted against
syslinux in Buildroot.
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-10-29 20:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-24 22:08 [Buildroot] [PATCH v2] boot/syslinux: Bump to 6.04-pre2 Alexander Sverdlin
2026-10-25 20:36 ` Thomas Petazzoni via buildroot
2026-10-26 20:45 ` Alexander Sverdlin
2026-10-27 4:54 ` Andreas Ziegler
2026-10-27 5:57 ` Alexander Sverdlin
2026-10-27 8:20 ` Thomas Petazzoni via buildroot
2026-10-27 15:12 ` Lance Fredrickson
2026-10-27 8:19 ` Thomas Petazzoni via buildroot
2026-10-28 4:48 ` Andreas Ziegler
2026-10-29 20:30 ` Thomas Petazzoni via buildroot [this message]
2026-10-30 5:39 ` Andreas Ziegler
2026-10-27 8:15 ` Thomas Petazzoni via buildroot
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=auOsS9x90TIovctY@windsurf \
--to=buildroot@buildroot.org \
--cc=alexander.sverdlin@gmail.com \
--cc=br025@umbiko.net \
--cc=thomas.petazzoni@bootlin.com \
/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