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: Mon, 24 Apr 2017 08:30:16 -0700 [thread overview]
Message-ID: <fd6f4279-949d-ef4d-e348-bd79804b4efe@infradead.org> (raw)
In-Reply-To: <f257820e-7010-72d8-c005-924a158ee4c1@ti.com>
On 04/24/17 04:40, Sekhar Nori wrote:
> Hi Randy,
>
> On Sunday 23 April 2017 07:52 AM, Randy Dunlap wrote:
>> 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> ?
>
> I hadn't, but I just checked with:
>
> $ make -C <kernelsrcdir>/tools iio O=<outputdir>
>
> Although there is an iio folder created under <outputdir>, the actual
> binaries are still built under <kernelsrcdir>/tools/iio. So I think
> there is some more work to be done to respect the O= option passed from
> command line.
>
> The behavior remains same with or without my patch.
Yes, agreed. This is a common problem in tools.
Thanks.
--
~Randy
next prev parent reply other threads:[~2017-04-24 15:30 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
2017-04-24 11:40 ` Sekhar Nori
2017-04-24 15:30 ` Randy Dunlap [this message]
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=fd6f4279-949d-ef4d-e348-bd79804b4efe@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®