From: Vinod Koul <vkoul@kernel.org>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Vladimir Oltean <olteanv@gmail.com>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Josua Mayer <josua@solid-run.com>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Tommaso Merciai <tommaso.merciai.xr@bp.renesas.com>,
linux-phy@lists.infradead.org, linux-mmc@vger.kernel.org,
linux-renesas-soc@vger.kernel.org, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH next] phy: renesas: rcar-gen3-usb2: Drop local devm_mux_state_get_optional()
Date: Thu, 12 Feb 2026 16:47:15 +0530 [thread overview]
Message-ID: <aY22u1rDDWuU53zP@vaman> (raw)
In-Reply-To: <CAPDyKFo92pOimvtGdN4yvFtFkc3vB+ex2OH10WmoKXcVSS+iAA@mail.gmail.com>
On 12-02-26, 11:39, Ulf Hansson wrote:
> On Wed, 11 Feb 2026 at 17:17, Vinod Koul <vkoul@kernel.org> wrote:
> > Should I drop the 8bb92fd7a0407792 and it makes things easier for
> > everyone and then we can pick fixed commit for 7.1 cycle..
>
> Well, my pull request for MMC was broken (the mux patches didn't get
> properly tested in linux-next, until it was too late), so Linus will
> not take it.
Yeah I saw that one, sorry for that
> At this point I would say that 8bb92fd7a0407792 is still a bit
> problematic as it uses the same name of the helper that the mux core
> intends to use. It would be better with a phy specific name for it, so
> it becomes easier to convert to the common mux helper, later on.
> Although, at this point it's still okay as is, as we will need to
> defer the mux core changes to v7.1 anyway.
>
> So up to you!
In that case, I can keep as is for now. We can rename the api as a fix
and proper changes can go in for 7.1
--
~Vinod
WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vkoul@kernel.org>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Vladimir Oltean <olteanv@gmail.com>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Josua Mayer <josua@solid-run.com>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Tommaso Merciai <tommaso.merciai.xr@bp.renesas.com>,
linux-phy@lists.infradead.org, linux-mmc@vger.kernel.org,
linux-renesas-soc@vger.kernel.org, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH next] phy: renesas: rcar-gen3-usb2: Drop local devm_mux_state_get_optional()
Date: Thu, 12 Feb 2026 16:47:15 +0530 [thread overview]
Message-ID: <aY22u1rDDWuU53zP@vaman> (raw)
In-Reply-To: <CAPDyKFo92pOimvtGdN4yvFtFkc3vB+ex2OH10WmoKXcVSS+iAA@mail.gmail.com>
On 12-02-26, 11:39, Ulf Hansson wrote:
> On Wed, 11 Feb 2026 at 17:17, Vinod Koul <vkoul@kernel.org> wrote:
> > Should I drop the 8bb92fd7a0407792 and it makes things easier for
> > everyone and then we can pick fixed commit for 7.1 cycle..
>
> Well, my pull request for MMC was broken (the mux patches didn't get
> properly tested in linux-next, until it was too late), so Linus will
> not take it.
Yeah I saw that one, sorry for that
> At this point I would say that 8bb92fd7a0407792 is still a bit
> problematic as it uses the same name of the helper that the mux core
> intends to use. It would be better with a phy specific name for it, so
> it becomes easier to convert to the common mux helper, later on.
> Although, at this point it's still okay as is, as we will need to
> defer the mux core changes to v7.1 anyway.
>
> So up to you!
In that case, I can keep as is for now. We can rename the api as a fix
and proper changes can go in for 7.1
--
~Vinod
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2026-02-12 11:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 10:53 [PATCH next] phy: renesas: rcar-gen3-usb2: Drop local devm_mux_state_get_optional() Geert Uytterhoeven
2026-02-10 10:53 ` Geert Uytterhoeven
2026-02-10 11:26 ` Tommaso Merciai
2026-02-10 11:26 ` Tommaso Merciai
2026-02-10 13:34 ` Ulf Hansson
2026-02-10 13:34 ` Ulf Hansson
2026-02-11 16:17 ` Vinod Koul
2026-02-11 16:17 ` Vinod Koul
2026-02-11 16:30 ` Geert Uytterhoeven
2026-02-11 16:30 ` Geert Uytterhoeven
2026-02-12 4:59 ` Vinod Koul
2026-02-12 4:59 ` Vinod Koul
2026-02-12 9:31 ` Vladimir Oltean
2026-02-12 9:31 ` Vladimir Oltean
2026-02-12 10:39 ` Ulf Hansson
2026-02-12 10:39 ` Ulf Hansson
2026-02-12 11:17 ` Vinod Koul [this message]
2026-02-12 11:17 ` Vinod Koul
2026-02-11 16:21 ` kernel test robot
2026-02-11 16:21 ` kernel test robot
2026-02-12 0:39 ` kernel test robot
2026-02-12 0:39 ` kernel test robot
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=aY22u1rDDWuU53zP@vaman \
--to=vkoul@kernel.org \
--cc=geert+renesas@glider.be \
--cc=josua@solid-run.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=olteanv@gmail.com \
--cc=tommaso.merciai.xr@bp.renesas.com \
--cc=ulf.hansson@linaro.org \
--cc=wsa+renesas@sang-engineering.com \
--cc=yoshihiro.shimoda.uh@renesas.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.