From: Andi Shyti <andi@etezian.org>
To: tt.rantala@gmail.com
Cc: trinity@vger.kernel.org, mikko.rapeli@iki.fi
Subject: Re: [PATCH] ioctls: btrfs-control: fix header inclusion order
Date: Wed, 24 Jul 2013 01:30:14 +0200 [thread overview]
Message-ID: <20130723233014.GB4249@jack.whiskey> (raw)
In-Reply-To: <1374608128-29846-1-git-send-email-andi@etezian.org>
> This patch enables older linux/btrfs.h where NULL is not
^^^
This was supposed to be newer, I'll come with patch v2
Andi
> recognized as a define. It gets rid of the following compiling
> error:
>
> In file included from ioctls/btrfs-control.c:5:0:
> /usr/include/linux/btrfs.h: In function ‘btrfs_err_str’:
> /usr/include/linux/btrfs.h:486:11: error: ‘NULL’ undeclared (first use in this function)
> return NULL;
> ^
>
> This is done by postponing the inclusion of btrf.h
>
> Signed-off-by: Andi Shyti <andi@etezian.org>
next prev parent reply other threads:[~2013-07-23 23:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 19:35 [PATCH] ioctls: btrfs-control: fix header inclusion order Andi Shyti
2013-07-23 23:30 ` Andi Shyti [this message]
2013-07-23 23:39 ` [PATCH v2] " Andi Shyti
2013-07-24 6:56 ` Tommi Rantala
2013-07-24 10:31 ` [PATCH v3] " Andi Shyti
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=20130723233014.GB4249@jack.whiskey \
--to=andi@etezian.org \
--cc=mikko.rapeli@iki.fi \
--cc=trinity@vger.kernel.org \
--cc=tt.rantala@gmail.com \
/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