Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:2 as permitted sender) client-ip=2620:137:e000::3:2;
MIME-Version: 1.0
References: <20231013091831.60a032c2@canb.auug.org.au> <CACRpkdaEVUfFg-O53NBiyWPsjx0VZVMKK7o2ikUMSCy0_AJUGQ@mail.gmail.com>
 <CAMuHMdX3LXZiRRAHSb1FU6nrgtPnyewbUwp7R9Rw2zbxziYz7w@mail.gmail.com> <CACRpkdYNRyL-hywayP97PsLvhEk_Dm4HdnYHHo9N50GXMuxWCg@mail.gmail.com>
In-Reply-To: <CACRpkdYNRyL-hywayP97PsLvhEk_Dm4HdnYHHo9N50GXMuxWCg@mail.gmail.com>
From:   Geert Uytterhoeven <geert@linux-m68k.org>
Date:   Fri, 13 Oct 2023 09:37:29 +0200
Message-ID: <CAMuHMdUSirm9mxjRMEh3uBeo71smOwKfuvmSrq6TauCs664mmQ@mail.gmail.com>
Subject: Re: linux-next: duplicate patch in the pinctrl tree
To:     Linus Walleij <linus.walleij@linaro.org>
Cc:     Stephen Rothwell <sfr@canb.auug.org.au>,
        Ralph Siemsen <ralph.siemsen@linaro.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux Next Mailing List <linux-next@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8BIT
Precedence: bulk

Hi Linus,

On Fri, Oct 13, 2023 at 9:14 AM Linus Walleij <linus.walleij@linaro.org> wrote:
> On Fri, Oct 13, 2023 at 9:10 AM Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> > On Fri, Oct 13, 2023 at 12:44 AM Linus Walleij <linus.walleij@linaro.org> wrote:
> > > On Fri, Oct 13, 2023 at 12:18 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > > > The following commit is also in Linus Torvalds' tree as a different commit
> > > > (but the same patch):
> > > >
> > > >   73394a1b2194 ("pinctrl: renesas: rzn1: Enable missing PINMUX")
> > > >
> > > > This is commit
> > > >
> > > >   f055ff23c331 ("pinctrl: renesas: rzn1: Enable missing PINMUX")
> > > >
> > > > in Linus' tree.
> > >
> > > I had to fix up the commit message, sorry,
> >
> > The only difference is your added SoB?
>
> No, I'm not that vain...

I don't see any other difference, though:

$ git help diff-commits
'diff-commits' is aliased to '!bash -c "colordiff -up <(git show $1)
<(git show $2) | less -R" #'
$ git diff-commits 73394a1b2194 f055ff23c331
--- /dev/fd/63  2023-10-13 09:30:50.809415961 +0200
+++ /dev/fd/62  2023-10-13 09:30:50.809415961 +0200
@@ -1,4 +1,4 @@
-commit 73394a1b2194694b66f7a0839a219ce0d16b64a3
+commit f055ff23c331f28aa4ace4b72dc56f63b9a726c8
 Author: Ralph Siemsen <ralph.siemsen@linaro.org>
 Date:   Wed Oct 4 16:00:08 2023 -0400

@@ -17,6 +17,7 @@ Date:   Wed Oct 4 16:00:08 2023 -0400
     Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
     Link: https://lore.kernel.org/r/20231004200008.1306798-1-ralph.siemsen@linaro.org
     Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
+    Signed-off-by: Linus Walleij <linus.walleij@linaro.org>

 diff --git a/drivers/pinctrl/renesas/Kconfig b/drivers/pinctrl/renesas/Kconfig
 index 77730dc548ed3c70..c8d519ca53eb7f31 100644

> > > I'll rebuild my branch for -next.
> >
> > I'm afraid that won't help, as the original one (from
> > renesas-pinctrl-fixes-for-v6.6) is also part of
> > renesas-pinctrl-for-v6.7, which I'm gonna send you a PR for later today.
> >
> > I guess we'll just have to live with it?
>
> It's fine if you drop it and rebase from my side, I understand the
> hashes will be different but the content is the same so it is the
> same tested.
>
> But I guess there could be reasons for not to, so then we can
> live with it I guess.

OK, I'll drop it from renesas-pinctrl-for-v6.7. I don't have any other
changes touching the same file.

Thanks!

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-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