From: Lee Jones <lee@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Arnd Bergmann <arnd@arndb.de>,
ARM <linux-arm-kernel@lists.infradead.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 mfd tree
Date: Fri, 30 May 2025 17:44:31 +0100 [thread overview]
Message-ID: <20250530164431.GB7758@google.com> (raw)
In-Reply-To: <20250526140400.54ac8a6c@canb.auug.org.au>
On Mon, 26 May 2025, Stephen Rothwell wrote:
> Hi all,
>
> The following commit is also in the arm-soc tree as a different commit
> (but the same patch):
>
> 0ffcf5f1e41c ("dt-bindings: mfd: qcom,tcsr: Add compatible for ipq5018")
>
> This is commit
>
> 1d2c5d5f3f44 ("dt-bindings: mfd: qcom,tcsr: Add compatible for ipq5018")
>
> in the arm-soc tree.
Why is this patch in the arm-soc tree?
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2025-05-30 17:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-26 4:04 linux-next: duplicate patch in the mfd tree Stephen Rothwell
2025-05-30 16:44 ` Lee Jones [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-14 3:42 Stephen Rothwell
2025-11-18 18:33 ` Lee Jones
2025-11-19 11:57 ` Ulf Hansson
2025-11-19 13:01 ` Lee Jones
2025-11-19 17:11 ` Ulf Hansson
2025-07-25 1:36 Stephen Rothwell
2025-07-25 11:35 ` Lee Jones
2025-07-25 11:48 ` Arnd Bergmann
2025-07-25 16:55 ` Sven Peter
2025-03-17 3:45 Stephen Rothwell
2025-03-17 22:51 ` Heiko Stübner
2024-09-05 6:42 Stephen Rothwell
2024-09-09 9:07 ` Lee Jones
2023-09-25 2:14 Stephen Rothwell
2023-02-21 6:27 Stephen Rothwell
2023-01-27 5:09 Stephen Rothwell
2023-01-27 9:33 ` Lee Jones
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=20250530164431.GB7758@google.com \
--to=lee@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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 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.