From: Andi Shyti <andi.shyti@kernel.org>
To: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
Thomas Richard <thomas.richard@bootlin.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i2c: cgbc: Convert to use struct platform_driver::remove()
Date: Wed, 20 Nov 2024 08:51:13 +0100 [thread overview]
Message-ID: <6nv6cngt3w5gj4hhlmqae26at3ey6ogwbskclsknycbzeuy4ia@jsjmx4nuhtss> (raw)
In-Reply-To: <xyxayycrcki4gjvgyc4x4onmsoxl24rf5ab4ybgpyggsrmdygr@v5xpdhphourb>
Hi Uwe,
On Wed, Nov 20, 2024 at 08:33:44AM +0100, Uwe Kleine-König wrote:
> On Wed, Nov 20, 2024 at 08:16:59AM +0100, Wolfram Sang wrote:
> > On Wed, Nov 20, 2024 at 08:01:20AM +0100, Andi Shyti wrote:
> > > > > This driver has not been merged yet.
> > > >
> > > > It is in Lee's MFD tree, and thus, in -next. It will go to Linus' tree
> > > > this mergewindow.
> > >
> > > right! I saw it but forgot about it... then I will pin this
> > > patch for later.
> >
> > Lee provided an immutable branch with all the patches. If you pull it
> > into your tree next time, you probably won't forget :)
>
> That would be fine. The patch was marked as "Not Applicable" in
> patchwork. For the time being I updated that to "Awaiting Upstream"
> (though that doesn't make it appear as actionable).
I updated it to "Not Applicable". I was going to set the proper
status, thanks for doing it.
> If you don't pull, be asserted that I will remember you as my quest to
> drop remove_new depends on that.
Thanks! :-)
Andi
prev parent reply other threads:[~2024-11-20 7:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 9:13 [PATCH] i2c: cgbc: Convert to use struct platform_driver::remove() Uwe Kleine-König
2024-11-19 22:40 ` Andi Shyti
2024-11-20 5:34 ` Wolfram Sang
2024-11-20 7:01 ` Andi Shyti
2024-11-20 7:16 ` Wolfram Sang
2024-11-20 7:33 ` Uwe Kleine-König
2024-11-20 7:51 ` Andi Shyti [this message]
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=6nv6cngt3w5gj4hhlmqae26at3ey6ogwbskclsknycbzeuy4ia@jsjmx4nuhtss \
--to=andi.shyti@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas.richard@bootlin.com \
--cc=u.kleine-koenig@baylibre.com \
--cc=wsa+renesas@sang-engineering.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