From: Stephen Boyd <sboyd@kernel.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Biju Das <biju.das.jz@bp.renesas.com>,
Michael Turquette <mturquette@baylibre.com>,
linux-clk@vger.kernel.org, kernel@pengutronix.de,
Wolfram Sang <wsa@kernel.org>
Subject: Re: [PATCH] clk: versaclock3: Switch to use i2c_driver's probe callback
Date: Tue, 01 Aug 2023 13:38:20 -0700 [thread overview]
Message-ID: <edb4501ba28b2b4be8ef3d8fa7eeba9b.sboyd@kernel.org> (raw)
In-Reply-To: <20230731081803.vua6hyxhofasvrsm@pengutronix.de>
Quoting Uwe Kleine-König (2023-07-31 01:18:03)
> > Hello,
> >
> > this driver appeared in next today. It would be great if this patch
> > could be added on top to not interfere with the quest to remove
> > .probe_new directly after v6.6-rc1.
>
> my eventual plan is to send the patch removing .probe_new() around
> v6.6-rc1 with the intention to get it into next early during the merge
> window. So if this patch doesn't make it in before v6.6-rc1, I'd send it
> together with the change dropping .probe_new() for Wolfram to apply as
> in today's next-20230731 there are only two drivers left making use of
> .probe_new (and the maintainer of the other driver already agreed to fix
> their driver with a patch going in via i2c, too).
>
> So in my order of preference, the options here are:
>
> - patch is applied via clk before v6.6-rc1
This option is now the plan.
> - patch is applied via i2c together with change dropping .probe_new()
> with a clk maintainer's Ack.
> - patch is ignored and goes in without an Ack via i2c.
>
next prev parent reply other threads:[~2023-08-01 20:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 7:18 [PATCH] clk: versaclock3: Switch to use i2c_driver's probe callback Uwe Kleine-König
2023-07-31 8:18 ` Uwe Kleine-König
2023-08-01 20:38 ` Stephen Boyd [this message]
2023-08-01 20:36 ` Stephen Boyd
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=edb4501ba28b2b4be8ef3d8fa7eeba9b.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=biju.das.jz@bp.renesas.com \
--cc=kernel@pengutronix.de \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=wsa@kernel.org \
/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