public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Arnd Bergmann" <arnd@arndb.de>, "Rob Herring" <robh@kernel.org>
Cc: "Olof Johansson" <olof@lixom.net>,
	"Palmer Dabbelt" <palmer@dabbelt.com>,
	"Paul Walmsley" <paul@pwsan.com>,
	ARM <linux-arm-kernel@lists.infradead.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	linux-next <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patches in the devicetree tree
Date: Tue, 9 Jul 2024 23:29:16 +1000	[thread overview]
Message-ID: <20240709232916.270d9927@canb.auug.org.au> (raw)
In-Reply-To: <f2ceee62-2612-42d1-b727-2f087acc6785@app.fastmail.com>

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

Hi all,

On Tue, 09 Jul 2024 15:15:44 +0200 "Arnd Bergmann" <arnd@arndb.de> wrote:
>
> On Tue, Jul 9, 2024, at 14:42, Rob Herring wrote:
> > On Tue, Jul 9, 2024 at 12:46 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:  
> >>
> >> The following commits are also in the arm-soc and risc-v trees as
> >> different commits (but the same patches):
> >>
> >>   0620bce64afa ("dt-bindings: riscv: cpus: add ref to interrupt-controller")
> >>   877097a2fab0 ("dt-bindings: interrupt-controller: convert marvell,mpic binding to YAML")
> >>   c7ce06684bf5 ("dt-bindings: interrupt-controller: riscv,cpu-intc: convert to dtschema")  
> >
> > I had to rebase my tree yesterday to drop a bunch of reserved-memory
> > restructuring that seems broken beyond repair. Maybe I'm going to have
> > to just do reverts instead. I had no knowledge that anyone had pulled
> > in my tree and how is it just these 3 commits? It should be at least
> > these:  
> 
> I picked up 
> 
> b1a4e71d4fc4 arm: dts: arm: Drop redundant fixed-factor clocks
> f7e642bcd622 dt-bindings: interrupt-controller: convert marvell,mpic binding to YAML
> 2af8d8a583a4 ARM: dts: armada-{370-xp,375,38x,39x}: Drop #size-cells from mpic node
> 
> from patchwork when they were sent to soc@kernel.org. I don't
> see the other ones in the arm-soc tree though, maybe they
> are merged elsewhere?

Yeah, the risc-v tree.  Sorry about that, I should probably have done 2
notifications.

-- 
Cheers,
Stephen Rothwell

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

  reply	other threads:[~2024-07-09 13:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-09  6:46 linux-next: duplicate patches in the devicetree tree Stephen Rothwell
2024-07-09 12:42 ` Rob Herring
2024-07-09 13:15   ` Arnd Bergmann
2024-07-09 13:29     ` Stephen Rothwell [this message]
2024-07-09 13:34     ` Rob Herring
  -- strict thread matches above, loose matches on Subject: below --
2025-11-17  3:37 Stephen Rothwell
2025-11-17 13:41 ` Rob Herring
2025-03-21  4:38 Stephen Rothwell
2025-03-21  8:55 ` Arnd Bergmann
2024-05-15  3:01 Stephen Rothwell
2024-05-15 13:50 ` Krzysztof Wilczyński
2024-05-15 14:34   ` Rob Herring
2024-05-15 14:54     ` Krzysztof Wilczyński
2024-01-21  9:33 Stephen Rothwell
2023-12-18  5:42 Stephen Rothwell
2023-12-18 14:07 ` Rob Herring

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=20240709232916.270d9927@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=palmer@dabbelt.com \
    --cc=paul@pwsan.com \
    --cc=robh@kernel.org \
    /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