From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: buildroot@buildroot.org, Romain Naour <romain.naour@gmail.com>
Subject: Re: [Buildroot] [PATCH 1/1] package/efl: bump to version 1.28.1
Date: Thu, 1 Jan 2026 17:12:16 +0100 [thread overview]
Message-ID: <20260101171216.4c560d17@windsurf> (raw)
In-Reply-To: <20251003225823.3871690-2-giulio.benetti@benettiengineering.com>
Hello Giulio,
Thanks for this work!
On Sat, 4 Oct 2025 00:58:23 +0200
Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:
> Some important addition and several bug fixes for gcc-15. Some of those
> fixes are committed but not part of version 1.28.1 so they are added as
> local patches while dropping old patches except the tslib one.
>
> See Release Notes of all versions:
> https://www.enlightenment.org/news/2025-03-17-efl-1.28.1
> https://www.enlightenment.org/news/2025-01-11-efl-1.28.0
> https://www.enlightenment.org/news/2023-12-23-efl-1.27.0
>
> Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
Applied to master, thanks!
You had forgotten two things:
- make check-package, which pointed issues in .checkpackageignore
- make legal-info, which pointed issues with license files
If you are brave and want to tackle upstreaming the patch 0001, it
would definitely be nice :-)
Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-01-01 16:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-03 22:58 [Buildroot] [PATCH 0/1] EFL bump to 1.28.1 Giulio Benetti
2025-10-03 22:58 ` [Buildroot] [PATCH 1/1] package/efl: bump to version 1.28.1 Giulio Benetti
2026-01-01 16:12 ` Thomas Petazzoni via buildroot [this message]
2026-01-04 13:29 ` Giulio Benetti
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=20260101171216.4c560d17@windsurf \
--to=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=romain.naour@gmail.com \
--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.