[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAMuHMdXmBeUwhiaLkwV4z2xb67PHBjyJnp3VEMfHv52KAmaQpA@mail.gmail.com>
Date: Tue, 3 Sep 2024 09:12:25 +0200
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Mike Turquette <mturquette@...libre.com>, Stephen Boyd <sboyd@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: duplicate patch in the clk tree
Hi Stephen,
On Tue, Sep 3, 2024 at 3:27 AM Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> The following commit is also in the renesas tree as a different commit
> (but the same patch):
>
> 042859e80d4b ("dt-bindings: clock: renesas: Document RZ/V2H(P) SoC CPG")
>
> This is commit
>
> afec1aba0860 ("dt-bindings: clock: renesas: Document RZ/V2H(P) SoC CPG")
>
> in the renesas tree.
Thanks, I am aware of this issue. Due to an oversight on my side
when queuing the RZ/V2H clock driver one month ago, I forgot to put
the RZ/V2H DT binding definitions on its own branch. As these binding
definitions are needed for the DTS part, too, I had the choice between
merging in lots of unrelated clock commits, or just duplicating the
aforementioned commit. Hence I picked the latter.
Sorry for the troubles.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Powered by blists - more mailing lists