From: Saul Wold <sgw@linux.intel.com>
To: "Woegerer, Paul" <Paul_Woegerer@mentor.com>,
openembedded-core@lists.openembedded.org
Cc: otavio@ossystems.com.br
Subject: Re: [PATCH 1/3] liburcu: Update to version 0.7.9
Date: Thu, 14 Nov 2013 10:45:33 -0800 [thread overview]
Message-ID: <52851A4D.7090107@linux.intel.com> (raw)
In-Reply-To: <52851768.9010602@mentor.com>
On 11/14/2013 10:33 AM, Woegerer, Paul wrote:
> On 11/14/2013 07:28 PM, Saul Wold wrote:
>> On 11/14/2013 04:34 AM, Paul Woegerer wrote:
>>> Signed-off-by: Paul Woegerer <paul_woegerer@mentor.com>
>>> ---
>>> meta/recipes-support/liburcu/{liburcu_0.7.7.bb => liburcu_0.7.9.bb}
>>> | 4 ++--
>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>> rename meta/recipes-support/liburcu/{liburcu_0.7.7.bb =>
>>> liburcu_0.7.9.bb} (81%)
>>>
>>> diff --git a/meta/recipes-support/liburcu/liburcu_0.7.7.bb
>>> b/meta/recipes-support/liburcu/liburcu_0.7.9.bb
>>> similarity index 81%
>>> rename from meta/recipes-support/liburcu/liburcu_0.7.7.bb
>>> rename to meta/recipes-support/liburcu/liburcu_0.7.9.bb
>>> index a75e92e..c8c4802 100644
>>> --- a/meta/recipes-support/liburcu/liburcu_0.7.7.bb
>>> +++ b/meta/recipes-support/liburcu/liburcu_0.7.9.bb
>>> @@ -9,8 +9,8 @@ LIC_FILES_CHKSUM =
>>> "file://LICENSE;md5=0f060c30a27922ce9c0d557a639b4fa3 \
>>>
>>> SRC_URI = "http://lttng.org/files/urcu/userspace-rcu-${PV}.tar.bz2"
>>>
>>> -SRC_URI[md5sum] = "d14de3ff32eb1ab9424b258599c8a6f3"
>>> -SRC_URI[sha256sum] =
>>> "8ab8a7d8fea47c09ceac24c9277f00da626bbd9426c973eb325b1baf33b4bdfb"
>>> +SRC_URI[md5sum] = "a625266e17437f91111ab4e736c5056f"
>>> +SRC_URI[sha256sum] =
>>> "a7e1f781773c953d5cc456aa92a3c6d2385c5f984d8d576dccfaf93dd14f1405"
>>>
>>> S = "${WORKDIR}/userspace-rcu-${PV}"
>>> CFLAGS_append_libc-uclibc = " -D_GNU_SOURCE"
>>>
>> We appear to have updated this to 0.8.0 already, will that be a problem?
>
> No problem. lttng-ust 2.3 works fine with urcu 0.8.x.
>
> I will send an update to 0.8.1 (see
> http://lists.lttng.org/pipermail/lttng-dev/2013-November/021744.html).
>
Ok, when you do so, can you do a small cleanup of moving the files
directory to liburcu, we are trying to clean that up incrementally.
Thanks
Sau!
> Thanks,
> Paul
>
>>
>> Sau!
>>
>
>
next prev parent reply other threads:[~2013-11-14 18:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-14 12:34 [PATCH 0/3] lttng: Update to lttng 2.3.1 (for userspace) Paul Woegerer
2013-11-14 12:34 ` [PATCH 1/3] liburcu: Update to version 0.7.9 Paul Woegerer
2013-11-14 18:28 ` Saul Wold
2013-11-14 18:33 ` Woegerer, Paul
2013-11-14 18:45 ` Saul Wold [this message]
2013-11-22 13:41 ` [PATCH] liburcu: Update to version 0.8.1 Paul Woegerer
2013-11-22 15:01 ` Woegerer, Paul
2013-11-14 12:34 ` [PATCH 2/3] lttng-ust: Update to version 2.3.1 Paul Woegerer
2013-11-14 12:34 ` [PATCH 3/3] lttng-tools: " Paul Woegerer
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=52851A4D.7090107@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=Paul_Woegerer@mentor.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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.