From: Lee Jones <lee@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
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: Mon, 9 Sep 2024 10:07:29 +0100 [thread overview]
Message-ID: <20240909090729.GB6556@google.com> (raw)
In-Reply-To: <20240905164254.71e53f73@canb.auug.org.au>
On Thu, 05 Sep 2024, Stephen Rothwell wrote:
> Hi all,
>
> The following commit is also in the sound-asoc tree as a different commit
> (but the same patch):
>
> 555fa39ba1fd ("dt-bindings: mfd: mediatek: Add codec property for MT6357 PMIC")
>
> This is commit
>
> 761cab667898 ("dt-bindings: mfd: mediatek: Add codec property for MT6357 PMIC")
>
> in the sound-asoc tree.
Looks like Mark accidentally applied it here:
https://lore.kernel.org/all/172544860860.19172.7052813450885034844.b4-ty@kernel.org/
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2024-09-09 9:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 6:42 linux-next: duplicate patch in the mfd tree Stephen Rothwell
2024-09-09 9:07 ` 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-05-26 4:04 Stephen Rothwell
2025-05-30 16:44 ` Lee Jones
2025-03-17 3:45 Stephen Rothwell
2025-03-17 22:51 ` Heiko Stübner
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=20240909090729.GB6556@google.com \
--to=lee@kernel.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--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.