From: Kent Gibson <warthog618@gmail.com>
To: Drew Fustini <drew@pdp7.com>
Cc: linux-gpio@vger.kernel.org
Subject: Re: [PATCH v2 0/2] gpio: add new SET_CONFIG ioctl() to gpio chardev
Date: Sun, 3 Nov 2019 07:14:11 +0800 [thread overview]
Message-ID: <20191102231344.GA3447@sol> (raw)
In-Reply-To: <20191102210205.GA26757@x1>
On Sat, Nov 02, 2019 at 10:02:05PM +0100, Drew Fustini wrote:
> On Thu, Oct 31, 2019 at 10:48:23PM +0800, Kent Gibson wrote:
> > The patch series is against Bart's gpio/for-next branch[1] with v4 of
> > my bias patch series "gpio: expose line bias flags to userspace" applied.
> > This is necessary to support setting of the bias flags introduced
> > there.
>
> I'd like to apply this to test but I wanted to check should I still be applying
> all the patches from "[PATCH v4 0/5] gpio: expose line bias flags to userspace"?
>
Yes, this patch series is based on top of the full bias patch series,
so I would apply the whole series. It definitely requires patch 1 and 4
from that series, as they define some of the flags it uses.
I don't have any corresponding updates for libgpiod yet - and even my
gpiod library only supports the new ioctl for testing.
I was holding off to see if the UAPI changes were ok and if Bart has
any preference on additions to the libgpiod API, but I should look into
that now.
Cheers,
Kent.
prev parent reply other threads:[~2019-11-02 23:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 14:48 [PATCH v2 0/2] gpio: add new SET_CONFIG ioctl() to gpio chardev Kent Gibson
2019-10-31 14:48 ` [PATCH v2 1/2] gpiolib: move validation of line handle flags into helper function Kent Gibson
2019-10-31 14:48 ` [PATCH v2 2/2] gpio: add new SET_CONFIG ioctl() to gpio chardev Kent Gibson
2019-11-02 21:02 ` [PATCH v2 0/2] " Drew Fustini
2019-11-02 23:14 ` Kent Gibson [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=20191102231344.GA3447@sol \
--to=warthog618@gmail.com \
--cc=drew@pdp7.com \
--cc=linux-gpio@vger.kernel.org \
/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.