From: Johan Hedberg <johan.hedberg@gmail.com>
To: Lucas De Marchi <lucas.demarchi@profusion.mobi>
Cc: linux-bluetooth@vger.kernel.org,
Lucas De Marchi <lucas.de.marchi@gmail.com>
Subject: Re: [PATCH BlueZ 1/7] build-sys: Define _GNU_SOURCE in config.h
Date: Wed, 5 Dec 2012 17:24:34 +0200 [thread overview]
Message-ID: <20121205152434.GA15812@x220> (raw)
In-Reply-To: <1354706575-4718-1-git-send-email-lucas.demarchi@profusion.mobi>
Hi Lucas,
On Wed, Dec 05, 2012, Lucas De Marchi wrote:
> Instead of defining _GNU_SOURCE in each source file (and potentially
> forgetting in some), tell the build system we use extensions and let it
> define _GNU_SOURCE in config.h.
> ---
> configure.ac | 1 +
> monitor/btsnoop.c | 1 -
> monitor/sdp.c | 1 -
> profiles/input/hog_device.c | 1 -
> src/adapter.c | 1 -
> src/mgmt.c | 1 -
> src/sdp-xml.c | 1 -
> src/textfile.c | 1 -
> tools/btsnoop.c | 1 -
> tools/ciptool.c | 1 -
> tools/hciattach.c | 1 -
> tools/rfcomm.c | 1 -
> 12 files changed, 1 insertion(+), 11 deletions(-)
All patches in this set have been applied. Thanks!
Johan
prev parent reply other threads:[~2012-12-05 15:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 11:22 [PATCH BlueZ 1/7] build-sys: Define _GNU_SOURCE in config.h Lucas De Marchi
2012-12-05 11:22 ` [PATCH BlueZ 2/7] Ensure config.h is included by using CPPFLAGS Lucas De Marchi
2012-12-05 11:22 ` [PATCH BlueZ 3/7] build-sys: Add missing force arg to symlink creation Lucas De Marchi
2012-12-05 11:22 ` [PATCH BlueZ 4/7] Use the entire include path for gdbus.h Lucas De Marchi
2012-12-05 11:22 ` [PATCH BlueZ 5/7] Use the entire include path for btio.h Lucas De Marchi
2012-12-05 11:22 ` [PATCH BlueZ 6/7] Reorder btio.h includes Lucas De Marchi
2012-12-05 11:22 ` [PATCH BlueZ 7/7] Use entire include path for gobex.h Lucas De Marchi
2012-12-05 15:24 ` Johan Hedberg [this message]
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=20121205152434.GA15812@x220 \
--to=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=lucas.de.marchi@gmail.com \
--cc=lucas.demarchi@profusion.mobi \
/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;
as well as URLs for NNTP newsgroup(s).