public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: Lee Jones <lee@kernel.org>, Stephen Rothwell <sfr@canb.auug.org.au>
Cc: 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, 17 Mar 2025 23:51:33 +0100	[thread overview]
Message-ID: <5872617.DvuYhMxLoT@diego> (raw)
In-Reply-To: <20250317144507.0938757b@canb.auug.org.au>

Hi Stephen, Lee,

Am Montag, 17. März 2025, 04:45:07 MEZ schrieb Stephen Rothwell:
> Hi all,
> 
> The following commit is also in the rockchip tree as a different commit
> (but the same patch):
> 
>   7f3e3e7228bb ("dt-bindings: mfd: syscon: Add rk3528 QoS register compatible")
> 
> This is commit
> 
>   19a634195c1a ("dt-bindings: mfd: syscon: Add rk3528 QoS register compatible")
> 
> in the rockchip tree.

dang, sorry about that.

With the qos compatible being a syscon, this _should_ go through the mfd
tree with Lee's Signed-off-by ... that it got in 7f3e3e7228bb .

I'm not sure how I managed to mess that up :-S .

In any case, as the commit 19a634195c1a already made its way from my tree
to the soc-tree [0], I'll create a revert so that this is fixed before the
merge-window.


Sorry for the mess and thanks for noticing
Heiko


[0] https://web.git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git/commit/?h=for-next&id=19a634195c1a



  reply	other threads:[~2025-03-17 22:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-17  3:45 linux-next: duplicate patch in the mfd tree Stephen Rothwell
2025-03-17 22:51 ` Heiko Stübner [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
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=5872617.DvuYhMxLoT@diego \
    --to=heiko@sntech.de \
    --cc=lee@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