From: Lee Jones <lee.jones@linaro.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: linux-kernel@vger.kernel.org,
Haojian Zhuang <haojian.zhuang@gmail.com>,
Daniel Mack <daniel@zonque.org>,
kernel@pengutronix.de, Robert Jarzmik <robert.jarzmik@free.fr>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 3/4] mfd: tc6387xb: Drop disable callback that is never called
Date: Mon, 20 Jun 2022 09:31:32 +0100 [thread overview]
Message-ID: <YrAwZCGjN+1NZ0ua@google.com> (raw)
In-Reply-To: <20220619083200.gx3ardiogbarlvzs@pengutronix.de>
On Sun, 19 Jun 2022, Uwe Kleine-König wrote:
> Hello Lee,
>
> On Wed, Jun 15, 2022 at 10:07:04PM +0100, Lee Jones wrote:
> > On Mon, 30 May 2022, Uwe Kleine-König wrote:
> >
> > > The driver never calls the disable callback, so drop the member from
> > > the platform struct and all callbacks from the actual platform datas.
> > >
> > > Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> > > ---
> > > arch/arm/mach-pxa/eseries.c | 1 -
> > > include/linux/mfd/tc6387xb.h | 1 -
> > > 2 files changed, 2 deletions(-)
> >
> > Applied, thanks.
>
> Are these already in a public tree? They are not in next and
> git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git#for-mfd-next
> doesn't contain commits that are not in v5.19-rc1.
>
> I assume they are still in an internal tree and I just need some
> patience until they are pushed out?
Correct. Patience is a virtue.
I'm back at my desk today after a week of travel.
Check -next tomorrow.
--
Lee Jones [李琼斯]
Principal Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-06-20 8:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-30 19:24 [PATCH 0/4] mfd: Some preparations for making platform remove callbacks return void Uwe Kleine-König
2022-05-30 19:24 ` [PATCH 2/4] mfd: t7l66xb: Drop platform disable callback Uwe Kleine-König
2022-06-15 21:06 ` Lee Jones
2022-05-30 19:24 ` [PATCH 3/4] mfd: tc6387xb: Drop disable callback that is never called Uwe Kleine-König
2022-06-15 21:07 ` Lee Jones
2022-06-19 8:32 ` Uwe Kleine-König
2022-06-20 8:31 ` Lee Jones [this message]
2022-05-30 19:24 ` [PATCH 4/4] mfd: tc6393xb: Make disable callback return void Uwe Kleine-König
2022-06-15 21:08 ` 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=YrAwZCGjN+1NZ0ua@google.com \
--to=lee.jones@linaro.org \
--cc=daniel@zonque.org \
--cc=haojian.zhuang@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robert.jarzmik@free.fr \
--cc=u.kleine-koenig@pengutronix.de \
/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).