public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Lee Jones <lee@kernel•org>, Mark Brown <broonie@kernel•org>,
	Liam Girdwood <lgirdwood@gmail•com>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: duplicate patch in the mfd tree
Date: Thu, 5 Sep 2024 16:42:54 +1000	[thread overview]
Message-ID: <20240905164254.71e53f73@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 358 bytes --]

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.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2024-09-05  6:42 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-05  6:42 Stephen Rothwell [this message]
2024-09-09  9:07 ` linux-next: duplicate patch in the mfd tree Lee Jones
  -- 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=20240905164254.71e53f73@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=broonie@kernel$(echo .)org \
    --cc=lee@kernel$(echo .)org \
    --cc=lgirdwood@gmail$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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