From: Vinod Koul <vkoul@kernel.org>
To: "Christian Marangi (Ansuel)" <ansuelsmth@gmail.com>
Cc: Neil Armstrong <neil.armstrong@linaro.org>,
Manivannan Sadhasivam <mani@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Lorenzo Bianconi <lorenzo@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v14 0/3] airoha: an7581: USB support
Date: Tue, 6 Oct 2026 13:16:37 +0200 [thread overview]
Message-ID: <asTYlWdkrlci37FB@parshuram> (raw)
In-Reply-To: <CA+_ehUxra53C2N8a0t73nLpS4DkaNSzE3STfhU7j3ZoQ9becyg@mail.gmail.com>
On 06-10-26, 13:07, Christian Marangi (Ansuel) wrote:
> Il giorno mar 6 ott 2026 alle ore 13:04 Vinod Koul <vkoul@kernel.org>
> > Okay so we have a cross tree dependency. I would like my tree to be
> > buildable and not depend on next.
> >
> > I can
> > a) get a signed tag for this from clk tree with the required patch,
> > merge and then apply this series
> > b) postpone to rc1
> >
> > Either works for me
> >
>
> Maybe "a" is better for other phy driver? The pcie move patch is blocking
> other airoha drivers currently.
>
> What is the procedure? In theory just the dt patch is needed, nothing else.
Please send me Pull Request with a signed tag from clk tree. This is
typical workflow. Is it soc clock on common clk tree? Stephan or someone
can generate this and I can pull into phy/next and then apply this
series
--
~Vinod
next prev parent reply other threads:[~2026-10-06 11:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 10:29 Christian Marangi
2026-10-06 10:29 ` [PATCH v14 1/3] dt-bindings: phy: Add documentation for Airoha AN7581 USB PHY Christian Marangi
2026-10-06 10:29 ` [PATCH v14 2/3] phy: move and rename Airoha PCIe PHY driver to dedicated directory Christian Marangi
2026-10-06 10:29 ` [PATCH v14 3/3] phy: airoha: Add support for Airoha AN7581 USB PHY Christian Marangi
2026-10-06 10:45 ` [PATCH v14 0/3] airoha: an7581: USB support Vinod Koul
2026-10-06 10:47 ` Christian Marangi (Ansuel)
2026-10-06 11:04 ` Vinod Koul
2026-10-06 11:07 ` Christian Marangi (Ansuel)
2026-10-06 11:16 ` Vinod Koul [this message]
2026-10-06 11:25 ` Christian Marangi (Ansuel)
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=asTYlWdkrlci37FB@parshuram \
--to=vkoul@kernel.org \
--cc=ansuelsmth@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=lorenzo@kernel.org \
--cc=mani@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=robh@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
all inboxes | Powered by JetHome®