From: Lee Jones <lee.jones@linaro.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-kernel@vger.kernel.org,
Aaro Koskinen <aaro.koskinen@iki.fi>,
Janusz Krzysztofik <jmkrzyszt@gmail.com>,
Tony Lindgren <tony@atomide.com>,
Cory Maccarrone <darkstar6262@gmail.com>,
linux-omap@vger.kernel.org, Lee Jones <lee@kernel.org>
Subject: Re: [PATCH] mfd/omap1: htc-i2cpld: Convert to a pure GPIO driver
Date: Mon, 5 Sep 2022 12:13:22 +0100 [thread overview]
Message-ID: <YxXZ0u7nKd+j7Bys@google.com> (raw)
In-Reply-To: <20220831085301.490906-1-linus.walleij@linaro.org>
On Wed, 31 Aug 2022, Linus Walleij wrote:
> Instead of passing GPIO numbers pertaining to ourselves through
> platform data, just request GPIO descriptors from our own GPIO
> chips and use them, and cut down on the unnecessary complexity.
>
> Cc: Aaro Koskinen <aaro.koskinen@iki.fi>
> Cc: Janusz Krzysztofik <jmkrzyszt@gmail.com>
> Cc: Tony Lindgren <tony@atomide.com>
> Cc: Cory Maccarrone <darkstar6262@gmail.com>
> Cc: linux-omap@vger.kernel.org
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> If one of the OMAP1 people can provide an ACK then it's best
> if Lee takes this into the MFD tree.
If you haven't already, could you please resend this to my kernel.org
account, as-per MAINTAINERS? Thanks Linus.
> ---
> arch/arm/mach-omap1/board-htcherald.c | 9 ----
> drivers/mfd/htc-i2cpld.c | 59 ++++++++++++---------------
> include/linux/htcpld.h | 2 -
> 3 files changed, 26 insertions(+), 44 deletions(-)
--
DEPRECATED: Please use lee@kernel.org
next prev parent reply other threads:[~2022-09-05 11:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 8:53 [PATCH] mfd/omap1: htc-i2cpld: Convert to a pure GPIO driver Linus Walleij
2022-09-05 11:13 ` Lee Jones [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-09-05 11:58 Linus Walleij
2022-09-08 9:35 ` Lee Jones
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=YxXZ0u7nKd+j7Bys@google.com \
--to=lee.jones@linaro.org \
--cc=aaro.koskinen@iki.fi \
--cc=darkstar6262@gmail.com \
--cc=jmkrzyszt@gmail.com \
--cc=lee@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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 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.