From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/lmbench: bump version
Date: Sat, 17 Jan 2026 09:55:01 +0100 [thread overview]
Message-ID: <aWtOVsmKA6SDZa0A@windsurf> (raw)
In-Reply-To: <20260102161448.1184855-1-bernd@kuhls.net>
Hello,
On Fri, Jan 02, 2026 at 05:14:47PM +0100, Bernd Kuhls wrote:
> Last release dates back to 2007, switch _SITE to active fork:
> https://sourceforge.net/p/lmbench/patches/3/#4472
>
> Removed patch 0009 which is included in this bump.
>
> Rebased remaining patches.
>
> Sent some existing patches to new active upstream repo and added
> Upstream: tags.
>
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
Applied, 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
prev parent reply other threads:[~2026-01-17 8:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-02 16:14 [Buildroot] [PATCH 1/1] package/lmbench: bump version Bernd Kuhls
2026-01-17 8:55 ` 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=aWtOVsmKA6SDZa0A@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.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