Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH next 1/4] lttng-tools: bump version to 2.9.0
Date: Wed, 30 Nov 2016 22:09:38 +0100	[thread overview]
Message-ID: <20161130220938.246d5b98@free-electrons.com> (raw)
In-Reply-To: <20161130170445.55222-1-Vincent.Riera@imgtec.com>

Hello,

On Wed, 30 Nov 2016 17:04:42 +0000, Vicente Olivert Riera wrote:
> Drop sha256 hash. The combination of md5 and sha1 hashes is enough.
> 
> Remove upstream patches:
> 
>  - 0001-Fix-snapshot-del-output-with-name-on-musl.patch
>    https://github.com/lttng/lttng-tools/commit/07f5023712313d73ab3feac62390a2d50457b7aa
> 
>  - 0002-Fix-strerror_r-behavior-is-glibc-specific.patch
>    https://github.com/lttng/lttng-tools/commit/b6dacfe27a91af50a1f81a2a7eadf4f34ca75769
> 
>  - 0003-Set-thread-stack-size-to-ulimit-soft-value.patch
>    https://github.com/lttng/lttng-tools/commit/1a1a34b40ab10a195633b1ed5e2e9b42fdae0a78
> 
> Release notes:
>   https://lists.lttng.org/pipermail/lttng-dev/2016-November/026763.html
> 
> Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
> ---
>  ...Fix-snapshot-del-output-with-name-on-musl.patch |  32 --
>  ...Fix-strerror_r-behavior-is-glibc-specific.patch |  30 --
>  ...et-thread-stack-size-to-ulimit-soft-value.patch | 431 ---------------------
>  package/lttng-tools/lttng-tools.hash               |   9 +-
>  package/lttng-tools/lttng-tools.mk                 |   2 +-
>  5 files changed, 4 insertions(+), 500 deletions(-)
>  delete mode 100644 package/lttng-tools/0001-Fix-snapshot-del-output-with-name-on-musl.patch
>  delete mode 100644 package/lttng-tools/0002-Fix-strerror_r-behavior-is-glibc-specific.patch
>  delete mode 100644 package/lttng-tools/0003-Set-thread-stack-size-to-ulimit-soft-value.patch

All four applied to next. For the last patch, I was worried that CMake
might have been mandatory. But the configure script properly checks if
cmake is available or not, and apparently acts properly if it's not
available, so it looks good.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      parent reply	other threads:[~2016-11-30 21:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-30 17:04 [Buildroot] [PATCH next 1/4] lttng-tools: bump version to 2.9.0 Vicente Olivert Riera
2016-11-30 17:04 ` [Buildroot] [PATCH next 2/4] lttng-modules: " Vicente Olivert Riera
2016-11-30 17:04 ` [Buildroot] [PATCH next 3/4] lttng-babeltrace: bump version to 1.5.0 Vicente Olivert Riera
2016-12-03 13:35   ` Thomas Petazzoni
2016-11-30 17:04 ` [Buildroot] [PATCH next 4/4] lttng-libust: bump version to 2.9.0 Vicente Olivert Riera
2016-11-30 17:53 ` [Buildroot] [PATCH next 1/4] lttng-tools: " Baruch Siach
2016-11-30 21:03   ` Thomas Petazzoni
2016-11-30 21:09 ` Thomas Petazzoni [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=20161130220938.246d5b98@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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