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" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] Revert "btrfs-progs: disable backtrace and define __always_inline"
Date: Wed, 14 Jan 2015 01:42:28 +0100	[thread overview]
Message-ID: <54B5BB74.7060707@wizzup.org> (raw)
In-Reply-To: <20150114004216.GR3685@twin.jikos.cz>

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

Hi,

On 14/01/15 01:42, David Sterba wrote:
> On Wed, Jan 14, 2015 at 01:31:34AM +0100, Merlijn Wajer wrote:
>>> This only works if you include features.h and I don't know if other libcs provide that.  Thanks,
>>
>> musl provides /usr/include/features.h and glibc does so as well. (Checked
>> on musl and glibc systems) Searching the web seems to suggest that uclibc
>> supports it as well.
> 
> I'd say that we care about these two right now.
> 
>> Would you be in favour of including features.h and checking for __GLIBC__ ?
> 
> Yes please.

Alright. I will send a patch tomorrow - it's definitely past bed time
here now. :-)

Sorry for the inconvenience.

Regards,
Merlijn


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

  reply	other threads:[~2015-01-14  0:43 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
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 [this message]
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=54B5BB74.7060707@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