All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Alexander Sverdlin <alexander.sverdlin@gmail.com>
Cc: buildroot@buildroot.org, Andreas Ziegler <br025@umbiko.net>
Subject: Re: [Buildroot] [PATCH v2] boot/syslinux: Bump to 6.04-pre2
Date: Tue, 27 Oct 2026 09:15:01 +0100	[thread overview]
Message-ID: <auBdSH403Z_zX2Vz@windsurf> (raw)
In-Reply-To: <e34f4a3f8aaee192923e3ecdde4a287a1cfaabda.camel@gmail.com>

On Mon, Oct 26, 2026 at 09:45:35PM +0100, Alexander Sverdlin wrote:

> > Does it make sense to keep syslinux? Even Wikipedia says it's
> > "discontinued". Do you still use it?
> 
> I'll be fine having it downstream. I just thought, there is still an
> interest [1] in this update ;-)

If you're still using it, totally fine with me to continue to have it
in Buildroot.

> Sorry, yes, all the dropped are "already applied", I will mention this
> in the commit message if you'll have interest in it.

Perfect.


> > And not this one, that you are removing?
> 
> So the patch 24 has partially reverted the patch 7, the latter is already merged
> upstream, but in different form (22d32c15ea96
> "Update the longjump calls to fit the new declaration").
> 
> Ultimately, patch 7 doesn't apply, patch 24 doesn't apply because patch
> 7 doesn't apply, but even if they would both apply, the net result will
> be exactly what 6.04-pre2 has upstream. And it's not buildable against the
> buildroot gnuefi package.

Hum, I'm not entirely sure to follow, but if the result builds/works,
that's what matters.

Can you send an updated version with a slightly improved commit
message, and then we will be good to go?

Thanks a lot!

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

      parent reply	other threads:[~2026-10-27  8:15 UTC|newest]

Thread overview: 11+ 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
2026-10-27  8:15     ` Thomas Petazzoni via buildroot [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=auBdSH403Z_zX2Vz@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.