public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Rob Herring <robh@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 devicetree tree
Date: Fri, 3 May 2024 08:13:41 +0100	[thread overview]
Message-ID: <20240503071341.GC1227636@google.com> (raw)
In-Reply-To: <20240503141548.68c2b106@canb.auug.org.au>

On Fri, 03 May 2024, Stephen Rothwell wrote:

> Hi all,
> 
> The following commit is also in the mfd tree as a different commit
> (but the same patch):
> 
>   828215066d88 ("dt-bindings: mfd: aspeed: Drop 'oneOf' for pinctrl node")

Rob, please remove this from your OF tree, thanks.

> This is commit
> 
>   8f553c27697b ("dt-bindings: mfd: aspeed: Drop 'oneOf' for pinctrl node")

-- 
Lee Jones [李琼斯]

  reply	other threads:[~2024-05-03  7:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-03  4:15 linux-next: duplicate patch in the devicetree tree Stephen Rothwell
2024-05-03  7:13 ` Lee Jones [this message]
2024-05-03 12:44 ` Rob Herring
  -- strict thread matches above, loose matches on Subject: below --
2025-08-13  2:14 Stephen Rothwell
2025-08-13 17:30 ` Bjorn Helgaas
2025-01-07  4:20 Stephen Rothwell
2025-01-07 14:23 ` Rob Herring
2024-09-16  6:01 Stephen Rothwell
2024-09-16 17:04 ` Wim Van Sebroeck
2024-09-05  6:40 Stephen Rothwell
2024-09-05  7:27 ` Krzysztof Wilczyński
2024-09-05 12:57   ` Rob Herring
2024-04-11  5:48 Stephen Rothwell
2024-04-11 12:40 ` Rob Herring
2024-03-11 22:51 Stephen Rothwell
2023-10-25 21:19 Stephen Rothwell
2023-10-26 12:43 ` Rob Herring
2023-01-18  0:19 Stephen Rothwell

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=20240503071341.GC1227636@google.com \
    --to=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=robh@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