From: Kris Bahnsen <kris@embeddedTS.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Mark Featherston <mark@embeddedTS.com>,
Kris Bahnsen <kris@embeddedTS.com>
Subject: [PATCH v3 0/2] gpio: ts4900: Do not set DAT and OE together
Date: Wed, 9 Mar 2022 17:16:15 -0800 [thread overview]
Message-ID: <20220310011617.29660-1-kris@embeddedTS.com> (raw)
Work around hardware race condition when setting DAT and OE in same
transaction. Also clean up license boilerplate and use SPDX.
I was not sure if it was preferred to make it a series or individual
patches. I went with series because "gpio: ts4900: Use SPDX header"
cannot cleanly apply by itself due to copyright year changes in the fix
commit. If this is not preferred, please let me know.
V3:
- Move addition of SPDX identifier to separate commit
- Remove license boilerplate in file
V2:
- Add Fixes tag
Kris Bahnsen (1):
gpio: ts4900: Use SPDX header
Mark Featherston (1):
gpio: ts4900: Do not set DAT and OE together
drivers/gpio/gpio-ts4900.c | 34 ++++++++++++++++++++--------------
1 file changed, 20 insertions(+), 14 deletions(-)
--
2.11.0
next reply other threads:[~2022-03-10 1:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 1:16 Kris Bahnsen [this message]
2022-03-10 1:16 ` [PATCH v3 1/2] gpio: ts4900: Do not set DAT and OE together Kris Bahnsen
2022-03-10 9:06 ` Bartosz Golaszewski
2022-03-10 14:48 ` Andy Shevchenko
2022-03-10 17:36 ` Kris Bahnsen
2022-03-10 19:30 ` Bartosz Golaszewski
2022-03-10 19:47 ` Kris Bahnsen
2022-03-11 11:25 ` Andy Shevchenko
2022-03-10 1:16 ` [PATCH v3 2/2] gpio: ts4900: Use SPDX header Kris Bahnsen
2022-03-10 9:06 ` 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=20220310011617.29660-1-kris@embeddedTS.com \
--to=kris@embeddedts.com \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@embeddedTS.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).