* linux-next: duplicate patch in the m68knommu tree
@ 2023-10-09 0:16 Stephen Rothwell
2023-10-09 2:00 ` Greg Ungerer
0 siblings, 1 reply; 3+ messages in thread
From: Stephen Rothwell @ 2023-10-09 0:16 UTC (permalink / raw)
To: Greg Ungerer, Geert Uytterhoeven
Cc: Linux Kernel Mailing List, Linux Next Mailing List
[-- Attachment #1: Type: text/plain, Size: 307 bytes --]
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
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: linux-next: duplicate patch in the m68knommu tree
2023-10-09 0:16 linux-next: duplicate patch in the m68knommu tree Stephen Rothwell
@ 2023-10-09 2:00 ` Greg Ungerer
2023-10-09 6:49 ` Geert Uytterhoeven
0 siblings, 1 reply; 3+ messages in thread
From: Greg Ungerer @ 2023-10-09 2:00 UTC (permalink / raw)
To: Stephen Rothwell, Geert Uytterhoeven
Cc: Linux Kernel Mailing List, Linux Next Mailing List
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: linux-next: duplicate patch in the m68knommu tree
2023-10-09 2:00 ` Greg Ungerer
@ 2023-10-09 6:49 ` Geert Uytterhoeven
0 siblings, 0 replies; 3+ messages in thread
From: Geert Uytterhoeven @ 2023-10-09 6:49 UTC (permalink / raw)
To: Greg Ungerer
Cc: Stephen Rothwell, Linux Kernel Mailing List, Linux Next Mailing List
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2023-10-09 6:49 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-10-09 0:16 linux-next: duplicate patch in the m68knommu tree Stephen Rothwell
2023-10-09 2:00 ` Greg Ungerer
2023-10-09 6:49 ` Geert Uytterhoeven
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).