From: "Karoly Pados" <pados@pados.hu>
To: "Johan Hovold" <johan@kernel.org>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
"Loic Poulain" <loic.poulain@linaro.org>
Subject: Re: [PATCH v6] USB: serial: ftdi_sio: implement GPIO support for FT-X devices
Date: Tue, 25 Sep 2018 10:47:26 +0000 [thread overview]
Message-ID: <d4f25792e9d0d008577021c85e01a809@pados.hu> (raw)
In-Reply-To: <20180925101523.GD3332@localhost>
>> gpiolib doesn't clear bits not in mask for you, so you need to OR with
>> *mask here to avoid setting random other bits.
>
> That was of course meant to be: *AND* with *mask.
>
Ah, okay, one question from my previous e-mail down.
next prev parent reply other threads:[~2018-09-25 10:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-24 14:31 [PATCH v6] USB: serial: ftdi_sio: implement GPIO support for FT-X devices Karoly Pados
2018-09-25 10:06 ` Johan Hovold
2018-09-25 10:15 ` Johan Hovold
2018-09-25 10:47 ` Karoly Pados [this message]
2018-09-25 10:46 ` Karoly Pados
2018-09-25 11:00 ` Johan Hovold
2018-09-25 11:11 ` Karoly Pados
2018-09-25 12:08 ` Johan Hovold
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=d4f25792e9d0d008577021c85e01a809@pados.hu \
--to=pados@pados.hu \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=loic.poulain@linaro.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 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).