From: Bjorn Helgaas <helgaas@kernel.org>
To: Andy Shevchenko <andy@kernel.org>
Cc: Vaibhav Gupta <vaibhavgupta40@gmail.com>,
linux-gpio@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>
Subject: [PATCH 0/5] GPIO PCH/ML-IOH consolidation baby steps
Date: Tue, 30 Nov 2021 16:08:36 -0600 [thread overview]
Message-ID: <20211130220841.2776562-1-helgaas@kernel.org> (raw)
From: Bjorn Helgaas <bhelgaas@google.com>
These are tiny cleanups to pch and ml-ioh to try to make them easier to
merge together. I can't really test either driver, so I'm not pushing too
hard on this.
If anybody wants to go further, Andy mentioned some docs here:
https://lore.kernel.org/lkml/CAHp75VfDcQXqmK9=4k4rqi7t2OZaVPC13b45vLY7fELr7zBG_Q@mail.gmail.com/
Bjorn Helgaas (5):
gpio: pch: Use .driver_data instead of checking Device IDs again
gpio: pch: Cache &pdev->dev to reduce repetition
gpio: ml-ioh: Cache &pdev->dev to reduce repetition
gpio: ml-ioh: Use BIT() to match gpio-pch.c
gpio: ml-ioh: Change whitespace to match gpio-pch.c
drivers/gpio/gpio-ml-ioh.c | 52 +++++++++++++++++++-------------------
drivers/gpio/gpio-pch.c | 42 +++++++++++++++---------------
2 files changed, 46 insertions(+), 48 deletions(-)
--
2.25.1
next reply other threads:[~2021-11-30 22:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-30 22:08 Bjorn Helgaas [this message]
2021-11-30 22:08 ` [PATCH 1/5] gpio: pch: Use .driver_data instead of checking Device IDs again Bjorn Helgaas
2021-11-30 22:08 ` [PATCH 2/5] gpio: pch: Cache &pdev->dev to reduce repetition Bjorn Helgaas
2021-11-30 22:08 ` [PATCH 3/5] gpio: ml-ioh: " Bjorn Helgaas
2021-11-30 22:08 ` [PATCH 4/5] gpio: ml-ioh: Use BIT() to match gpio-pch.c Bjorn Helgaas
2021-11-30 22:08 ` [PATCH 5/5] gpio: ml-ioh: Change whitespace " Bjorn Helgaas
2021-12-01 13:08 ` [PATCH 0/5] GPIO PCH/ML-IOH consolidation baby steps Andy Shevchenko
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=20211130220841.2776562-1-helgaas@kernel.org \
--to=helgaas@kernel.org \
--cc=andy@kernel.org \
--cc=bhelgaas@google.com \
--cc=linux-gpio@vger.kernel.org \
--cc=vaibhavgupta40@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).