Hi all,
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.
--
Cheers,
Stephen Rothwell
Hi Stephen,
On 9/10/23 10:16, Stephen Rothwell wrote:
> Hi all,
>
> 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.
Regards
Greg
Hi Greg,
On Mon, Oct 9, 2023 at 4:00 AM Greg Ungerer <[email protected]> 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 -- [email protected]
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