Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Merlijn Wajer <merlijn@wizzup.org>
To: dsterba@suse.cz, Josef Bacik <jbacik@fb.com>,
	linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Revert "btrfs-progs: disable backtrace and define __always_inline"
Date: Wed, 14 Jan 2015 01:19:06 +0100	[thread overview]
Message-ID: <54B5B5FA.20904@wizzup.org> (raw)
In-Reply-To: <20150114001341.GP3685@twin.jikos.cz>

[-- Attachment #1: Type: text/plain, Size: 557 bytes --]

Hi,

On 14/01/15 01:13, David Sterba wrote:
> On Tue, Jan 13, 2015 at 05:20:19PM -0500, Josef Bacik wrote:
>> This reverts commit c2691f807ddd2c6b261c5707f6838a45d9275390 as it breaks
>> backtracing on actual glibc environments.
> 
> This is to support musl libc. If it does not work then the test is wrong
> and should be fixed. CCed the author.

Thanks for letting me know. It unfortunately seems like I made a
mistake: it should be __GLIBC__ and not __glibc__.

Sorry about that. Would you like me to create a patch?

Regards,
Merlijn


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 884 bytes --]

  reply	other threads:[~2015-01-14  0:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-13 22:20 [PATCH] Revert "btrfs-progs: disable backtrace and define __always_inline" Josef Bacik
2015-01-14  0:13 ` David Sterba
2015-01-14  0:19   ` Merlijn Wajer [this message]
2015-01-14  0:26     ` Josef Bacik
2015-01-14  0:31       ` Merlijn Wajer
2015-01-14  0:39         ` Josef Bacik
2015-01-14  0:42         ` David Sterba
2015-01-14  0:42           ` Merlijn Wajer
2015-01-14  0:19   ` Josef Bacik

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=54B5B5FA.20904@wizzup.org \
    --to=merlijn@wizzup.org \
    --cc=dsterba@suse.cz \
    --cc=jbacik@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    /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