From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Kent Gibson <warthog618@gmail.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-gpio@vger.kernel.org,
Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: [libgpiod][PATCH 0/2] treewide: remove ctxless API
Date: Thu, 12 Nov 2020 12:06:40 +0100 [thread overview]
Message-ID: <20201112110642.14903-1-brgl@bgdev.pl> (raw)
From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
As I mentioned in another thread: the context-less API seems to be unused
outside the gpio-tools. There's no reason to keep it in v2 then. Let's
remove it and convert gpio-tools to regular API.
The tools are converted in a rather quick and dirty way because I don't want
to spend a lot of time on something that'll be modified soon once we convert
the library to using uAPI v2.
All tests still pass.
Bartosz Golaszewski (2):
core: provide gpiod_line_bulk_clear()
ctxless: drop all context-less interfaces
include/gpiod.h | 412 +--------------------------------
lib/Makefile.am | 2 +-
lib/core.c | 8 +-
lib/ctxless.c | 456 -------------------------------------
tests/Makefile.am | 1 -
tests/tests-ctxless.c | 375 ------------------------------
tools/gpio-tools-test.bats | 12 +-
tools/gpiofind.c | 25 +-
tools/gpioget.c | 36 ++-
tools/gpiomon.c | 177 +++++++-------
tools/gpioset.c | 42 +++-
tools/tools-common.c | 6 +-
12 files changed, 182 insertions(+), 1370 deletions(-)
delete mode 100644 lib/ctxless.c
delete mode 100644 tests/tests-ctxless.c
--
2.29.1
next reply other threads:[~2020-11-12 11:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 11:06 Bartosz Golaszewski [this message]
2020-11-12 11:06 ` [libgpiod][PATCH 1/2] core: provide gpiod_line_bulk_clear() Bartosz Golaszewski
2020-11-13 8:41 ` Bartosz Golaszewski
2020-11-12 11:06 ` [libgpiod][PATCH 2/2] ctxless: drop all context-less interfaces Bartosz Golaszewski
2020-11-17 14:00 ` [libgpiod][PATCH 0/2] treewide: remove ctxless API Bartosz Golaszewski
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=20201112110642.14903-1-brgl@bgdev.pl \
--to=brgl@bgdev.pl \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bgolaszewski@baylibre.com \
--cc=linux-gpio@vger.kernel.org \
--cc=warthog618@gmail.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).