linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Linus Walleij <linus.walleij@linaro.org>,
	Alexandre Courbot <gnurou@gmail.com>,
	linux-gpio@vger.kernel.org,
	Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: [PATCH v2 0/3] tools/gpio: switch to tools buildsystem
Date: Sat, 18 Jun 2016 18:24:45 +0300	[thread overview]
Message-ID: <1466263488-94457-1-git-send-email-andriy.shevchenko@linux.intel.com> (raw)

Current environment is not allowed to easily build the tools.
Move to tools buildsystem to allow user build gpio tools using only existing
kernel sources. Besides that support O=/path/to/build/dir option.

In v2:
- remove $(Q) for now for shell commands
- add cover letter

Andy Shevchenko (3):
  tools/gpio: remove old Makefile
  tools/gpio: move to tools buildsystem
  tools/gpio: add install section

 tools/Makefile      |  7 +++--
 tools/gpio/Build    |  3 ++
 tools/gpio/Makefile | 85 ++++++++++++++++++++++++++++++++++++++++++++++++-----
 3 files changed, 84 insertions(+), 11 deletions(-)
 create mode 100644 tools/gpio/Build

-- 
2.8.1


             reply	other threads:[~2016-06-18 15:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-18 15:24 Andy Shevchenko [this message]
2016-06-18 15:24 ` [PATCH v2 1/3] tools/gpio: remove old Makefile Andy Shevchenko
2016-06-18 15:24 ` [PATCH v2 2/3] tools/gpio: move to tools buildsystem Andy Shevchenko
2016-06-18 15:24 ` [PATCH v2 3/3] tools/gpio: add install section Andy Shevchenko
2016-06-19 13:07 ` [PATCH v2 0/3] tools/gpio: switch to tools buildsystem Alexandre Courbot
2016-06-19 13:52   ` Andy Shevchenko
2016-06-19 14:00     ` Alexandre Courbot

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=1466263488-94457-1-git-send-email-andriy.shevchenko@linux.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=gnurou@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.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;
as well as URLs for NNTP newsgroup(s).