From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 5/7] lttng-tools: make the dependency on lttng-libust optional
Date: Sun, 05 Feb 2012 11:17:01 +0100 [thread overview]
Message-ID: <87aa4xshya.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <cc297d07bc7c92e8c986efe0dde859a7e67436e3.1328366921.git.thomas.petazzoni@free-electrons.com> (Thomas Petazzoni's message of "Sat, 4 Feb 2012 15:48:46 +0100")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Thomas> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Committed, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2012-02-05 10:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-04 14:48 [Buildroot] [pull request] Pull request for branch for-2012.02/lttng-uclibc-fixes Thomas Petazzoni
2012-02-04 14:48 ` [Buildroot] [PATCH 1/7] liburcu: add patch to fix build with uClibc Thomas Petazzoni
2012-02-05 10:00 ` Peter Korsgaard
2012-02-05 10:07 ` Thomas Petazzoni
2012-02-04 14:48 ` [Buildroot] [PATCH 2/7] lttng-tools: fix build on uClibc due to sync_file_range() Thomas Petazzoni
2012-02-05 10:11 ` Peter Korsgaard
2012-02-04 14:48 ` [Buildroot] [PATCH 3/7] lttng-babeltrace: make sure WCHAR and LARGEFILE are enabled Thomas Petazzoni
2012-02-05 10:15 ` Peter Korsgaard
2012-02-04 14:48 ` [Buildroot] [PATCH 4/7] lttng-libust: add the dependency on util-linux Thomas Petazzoni
2012-02-05 10:15 ` Peter Korsgaard
2012-02-04 14:48 ` [Buildroot] [PATCH 5/7] lttng-tools: make the dependency on lttng-libust optional Thomas Petazzoni
2012-02-05 10:17 ` Peter Korsgaard [this message]
2012-02-04 14:48 ` [Buildroot] [PATCH 6/7] lttng-libust: add patch to fix build issue when C++ support is not available Thomas Petazzoni
2012-02-05 10:28 ` Peter Korsgaard
2012-02-04 14:48 ` [Buildroot] [PATCH 7/7] lttng-babeltrace: fix build on uClibc due to missing posix_fallocate() Thomas Petazzoni
2012-02-05 13:41 ` Peter Korsgaard
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=87aa4xshya.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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