Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org,
	Philippe Proulx <eeppeliteloop@gmail.com>,
	Devin Steffler <devin.buildroot@gmail.com>
Subject: Re: [Buildroot] [PATCH 4/4] package/lttng-libust: bump to version 2.14.0
Date: Thu, 1 Jan 2026 16:11:02 +0100	[thread overview]
Message-ID: <20260101161102.5e396956@windsurf> (raw)
In-Reply-To: <20251115164828.1519438-4-bernd@kuhls.net>

On Sat, 15 Nov 2025 17:48:27 +0100
Bernd Kuhls <bernd@kuhls.net> wrote:

> From: Devin Steffler <devin.buildroot@gmail.com>
> 
> This is the third of three patches relating to lttng-modules 2.13.10 not compiling with buildroot.
> 
> Since I am submitting a patch to bump lttng-modules to 2.13.17 and lttng-libust is a tightly related package,
> I am also submitting this patch to bump lttng-libust to 2.13.8 (the latest version at this time).
> 
> The chanagelog for lttng-libust 2.14.0 can be found here:
> https://git.lttng.org/?p=lttng-ust.git;a=blob;f=ChangeLog;h=1ddf7956cd80674f8bb0cec4b9362a9b1bf943b4;hb=refs/heads/stable-2.14
> 
> Signed-off-by: Devin Steffler <devin.buildroot@gmail.com>
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
> [Bernd:
>  - bumped to 2.14.0, updated link to changelog
>  - rebased patch 0001 due to upstream commit:
>    https://git.lttng.org/?p=lttng-ust.git;a=commitdiff;h=464c475658ae29039b3b9e769b5b02195688a94a
>  - updated license files and hashes due to upstream commit:
>    https://git.lttng.org/?p=lttng-ust.git;a=commit;h=e03d7c66c57bf268b87296566a5160039f35ccfb
>  - added dependency to host-python-setuptools due to upstream commit:
>    https://git.lttng.org/?p=lttng-ust.git;a=commitdiff;h=cb80e2fb106d56b4a0ae9c0480a368572f4d0d35]
> 
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
> ---
>  .../0001-configure.ac-add-disable-tests.patch      | 10 ++++++----
>  package/lttng-libust/lttng-libust.hash             | 14 +++++++-------
>  package/lttng-libust/lttng-libust.mk               | 11 ++++++++---
>  3 files changed, 21 insertions(+), 14 deletions(-)

Applied with a reworded commit log (and line wrapped to 80 columns).
Thanks!

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

  reply	other threads:[~2026-01-01 15:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-15 16:48 [Buildroot] [PATCH 1/4] package/liburcu: bump version to 0.15.5 Bernd Kuhls
2025-11-15 16:48 ` [Buildroot] [PATCH 2/4] package/lttng-modules: bump to version 2.14.3 Bernd Kuhls
2026-01-01 15:10   ` Thomas Petazzoni via buildroot
2025-11-15 16:48 ` [Buildroot] [PATCH 3/4] package/lttng-tools: bump to version 2.14.0 Bernd Kuhls
2026-01-01 15:10   ` Thomas Petazzoni via buildroot
2025-11-15 16:48 ` [Buildroot] [PATCH 4/4] package/lttng-libust: " Bernd Kuhls
2026-01-01 15:11   ` Thomas Petazzoni via buildroot [this message]
2026-01-01 15:08 ` [Buildroot] [PATCH 1/4] package/liburcu: bump version to 0.15.5 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=20260101161102.5e396956@windsurf \
    --to=buildroot@buildroot.org \
    --cc=bernd@kuhls.net \
    --cc=devin.buildroot@gmail.com \
    --cc=eeppeliteloop@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox