From: Jonathan Cameron <jic23@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
Hartmut Knaack <knaack.h@gmx.de>,
eter Meerwald-Stadler <pmeerw@pmeerw.net>,
linux-iio@vger.kernel.org, David Lechner <david@lechnology.com>
Subject: Re: [PATCH v1 1/2] iio: tools: move to tools buildsystem
Date: Wed, 9 Aug 2017 14:31:23 +0100 [thread overview]
Message-ID: <20170809143123.560732fb@archlinux> (raw)
In-Reply-To: <1501602838.29303.337.camel@linux.intel.com>
On Tue, 01 Aug 2017 18:53:58 +0300
Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
> On Sun, 2017-07-30 at 17:28 +0100, Jonathan Cameron wrote:
> > On Sat, 29 Jul 2017 03:36:04 +0300
> > Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
> >
> > > There is a nice buildsystem dedicated for userspace tools in Linux
> > > kernel tree.
> > > Switch iio target to be built by it.
> > >
> > > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> >
> > Looks very nice to me (and very very similar to gpio tools
> > which makes checking it is sane easy ;)
>
> Thanks for review!
>
> > Would like this to sit on the list a little while longer
> > in case someone with more Make foo than me wanders by
> > and spots something.
>
> Of course!
Long enough. Applied to the togreg branch of iio.git.
Thanks,
Jonathan
>
>
prev parent reply other threads:[~2017-08-09 13:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-29 0:36 [PATCH v1 1/2] iio: tools: move to tools buildsystem Andy Shevchenko
2017-07-29 0:36 ` [PATCH v1 2/2] iio: tools: add install section Andy Shevchenko
2017-07-30 16:30 ` Jonathan Cameron
2017-07-30 16:28 ` [PATCH v1 1/2] iio: tools: move to tools buildsystem Jonathan Cameron
2017-08-01 15:53 ` Andy Shevchenko
2017-08-09 13:31 ` Jonathan Cameron [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=20170809143123.560732fb@archlinux \
--to=jic23@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=david@lechnology.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.