From: Vinod Koul <vkoul@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Kishon Vijay Abraham I <kishon@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patch in the phy-next tree
Date: Wed, 13 Aug 2025 12:20:05 +0530 [thread overview]
Message-ID: <aJw1na9hExTLx-lB@vaman> (raw)
In-Reply-To: <20250813125510.186a1636@canb.auug.org.au>
On 13-08-25, 12:55, Stephen Rothwell wrote:
> Hi all,
>
> The following commit is also in the phy tree as a different commit
> (but the same patch):
>
> bc9c59c46b35 ("dt-bindings: phy: qcom,sc8280xp-qmp-pcie-phy: Update pcie phy bindings")
>
> This is commit
>
> aac1256a41cf ("dt-bindings: phy: qcom,sc8280xp-qmp-pcie-phy: Update pcie phy bindings")
>
> in the phy tree.
Thanks for the report. This is a fix so dropped from next, not sure how
this got applied to both!
--
~Vinod
next prev parent reply other threads:[~2025-08-13 6:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 2:55 linux-next: duplicate patch in the phy-next tree Stephen Rothwell
2025-08-13 6:50 ` Vinod Koul [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-06 4:24 Stephen Rothwell
2024-12-09 3:33 Stephen Rothwell
2023-01-19 4:36 Stephen Rothwell
2023-01-19 6:14 ` Vinod Koul
2023-01-19 13:26 ` Thierry Reding
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=aJw1na9hExTLx-lB@vaman \
--to=vkoul@kernel.org \
--cc=kishon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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