From: Randy Dunlap <rdunlap@infradead.org>
To: Sekhar Nori <nsekhar@ti.com>, Jonathan Cameron <jic23@kernel.org>
Cc: Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] tools/iio: Use include/uapi with __EXPORTED_HEADERS__
Date: Sat, 22 Apr 2017 19:22:35 -0700 [thread overview]
Message-ID: <0a357589-7169-5cff-e842-657b52049b15@infradead.org> (raw)
In-Reply-To: <5cfc29b0d8fa6c5bd97e59f7ab0ff718132efdec.1492777014.git.nsekhar@ti.com>
On 04/21/17 05:31, Sekhar Nori wrote:
> Use the local uapi headers to keep in sync with "recently" added enum
> values like IIO_UVINDEX.
>
> Build tested using:
> $ make -C <kernelsrcdir> tools/iio
> $ make -C <kernelsrcdir>/tools iio
> $ make -C <kernelsrcdir>/tools/iio
Hi,
Did you do any testing with O=<outputdir> ?
Thanks.
> This follows a strategy similar to that used by tools/hv, tools/net and
> tools/leds among others.
>
> Cc: Randy Dunlap <rdunlap@infradead.org>
> Cc: Jonathan Cameron <jic23@kernel.org>
> Signed-off-by: Sekhar Nori <nsekhar@ti.com>
> ---
> Change since v1:
> Shift to a strategy similar to that used by other makefiles in
> tools/ folder. v1 posting here: https://patchwork.kernel.org/patch/9674937/
>
> tools/iio/Makefile | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/iio/Makefile b/tools/iio/Makefile
> index 5446d625e17d..8f08e03a9a5e 100644
> --- a/tools/iio/Makefile
> +++ b/tools/iio/Makefile
> @@ -1,5 +1,5 @@
> CC = $(CROSS_COMPILE)gcc
> -CFLAGS += -Wall -g -D_GNU_SOURCE
> +CFLAGS += -Wall -g -D_GNU_SOURCE -D__EXPORTED_HEADERS__ -I../../include/uapi -I../../include
>
> BINDIR=usr/bin
> INSTALL_PROGRAM=install -m 755 -p
>
--
~Randy
next prev parent reply other threads:[~2017-04-23 2:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 12:31 Sekhar Nori
2017-04-23 2:22 ` Randy Dunlap [this message]
2017-04-24 11:40 ` Sekhar Nori
2017-04-24 15:30 ` Randy Dunlap
2017-04-27 5:33 ` Jonathan Cameron
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=0a357589-7169-5cff-e842-657b52049b15@infradead.org \
--to=rdunlap@infradead.org \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=pmeerw@pmeerw.net \
/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
all inboxes | Powered by JetHome®