Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:3 as permitted sender) client-ip=2620:137:e000::3:3;
MIME-Version: 1.0
References: <20231009111609.13ac1edb@canb.auug.org.au> <f0d0e8ad-8391-44f3-90e0-d2325daebb64@linux-m68k.org>
In-Reply-To: <f0d0e8ad-8391-44f3-90e0-d2325daebb64@linux-m68k.org>
From:   Geert Uytterhoeven <geert@linux-m68k.org>
Date:   Mon, 9 Oct 2023 08:49:08 +0200
Message-ID: <CAMuHMdVo-H+q+X8XCZrVVG3W05B53=ttQ3LUcqbJkCV0-zWTaA@mail.gmail.com>
Subject: Re: linux-next: duplicate patch in the m68knommu tree
To:     Greg Ungerer <gerg@linux-m68k.org>
Cc:     Stephen Rothwell <sfr@canb.auug.org.au>,
        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 Greg,

On Mon, Oct 9, 2023 at 4:00 AM Greg Ungerer <gerg@linux-m68k.org> wrote:
> On 9/10/23 10:16, Stephen Rothwell wrote:
> > The following commit is also in the m68k tree as a different commit
> > (but the same patch):
> >
> >    af580d01acc3 ("m68k: use kernel's generic libgcc functions")
> >
> > The is commit
> >
> >    a0938a8e2fb3 ("m68k: Use kernel's generic libgcc functions")
> >
> > in the m68k tree.
>
> Sorry, yes, fixed now. I removed it from the m68kmnommu git tree.

Thanks, I wasn't aware you had planned to queue it in the m68knommu
tree.  Sorry for not checking linux-next before.

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