From: Greg Ungerer <gerg@linux-m68k.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patch in the m68knommu tree
Date: Mon, 9 Oct 2023 12:00:05 +1000 [thread overview]
Message-ID: <f0d0e8ad-8391-44f3-90e0-d2325daebb64@linux-m68k.org> (raw)
In-Reply-To: <20231009111609.13ac1edb@canb.auug.org.au>
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
next prev parent reply other threads:[~2023-10-09 2:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 0:16 Stephen Rothwell
2023-10-09 2:00 ` Greg Ungerer [this message]
2023-10-09 6:49 ` Geert Uytterhoeven
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f0d0e8ad-8391-44f3-90e0-d2325daebb64@linux-m68k.org \
--to=gerg@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®