On Wed, 14 Feb 2024 at 09:35, Geert Uytterhoeven <geert@xxxxxxxxxxxxxx> wrote: > > Hi Ulf, > > On Wed, Jan 31, 2024 at 3:56 PM Geert Uytterhoeven <geert@xxxxxxxxxxxxxx> wrote: > > On Tue, Jan 30, 2024 at 2:11 PM Ulf Hansson <ulf.hansson@xxxxxxxxxx> wrote: > > > On Thu, 25 Jan 2024 at 16:34, Geert Uytterhoeven > > > <geert+renesas@xxxxxxxxx> wrote: > > > > This patch series adds initial support for the Renesas R-Car V4M > > > > (R8A779G0) SoC and the Renesas Gray Hawk Single development board. > > > > > > > > As both driver code and DTS have hard dependencies on DT binding > > > > definitions, most patches in this series are supposed to go in through > > > > the renesas-devel and/or renesas-clk trees, using a shared branch for DT > > > > binding definitions, as usual. For the PM domain patches (03, 04, 09), > > > > Ulf already offered to apply these to his pmdomain tree, and provide an > > > > immutable "dt" branch, to be pulled in my renesas-devel tree. > > > > > > Patch 3,4 and 9 (I dropped the copyright line in patch9, as pointed > > > out by Niklas) applied for next, thanks! > > > > > > Patch 3,4 are also available at the immutable dt branch for you to pull in. > > > > Thank you! > > > > I have pulled the immutable branch, added the remaining DT binding > > definitions, and queued all remaining patches. > > It looks like you have applied copies of all commits on the "dt" > branch to the "next" > branch, so now there are two copies? > > See the output of "git range-diff v6.8-rc1..pmdomain/dt > v6.8-rc4..pmdomain/next". I screwed up - and thanks for pointing this out! Problem is taken care of now. Kind regards Uffe
