From: Andreas Schwab <schwab@linux-m68k.org>
To: Greg Ungerer <gerg@snapgear.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
linux-m68k@vger.kernel.org, uclinux-dev@uclinux.org,
Greg Ungerer <gerg@uclinux.org>
Subject: Re: [PATCH v3 5/6] m68k: remove duplicate memcpy() implementation
Date: Tue, 24 May 2011 09:34:11 +0200 [thread overview]
Message-ID: <m31uzoy2ks.fsf@linux-m68k.org> (raw)
In-Reply-To: <4DDAF3F9.30209@snapgear.com> (Greg Ungerer's message of "Tue, 24 May 2011 09:55:37 +1000")
Greg Ungerer <gerg@snapgear.com> writes:
> m68k-linux-gcc (GCC) 4.5.1
Your compiler is too new :-) (This has been reorganized completely in 4.3.)
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2011-05-24 7:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-21 0:24 [PATCH v3 0/6] m68knommu: merge and clean up of arch/m68k/lib files gerg
2011-04-21 0:24 ` [PATCH v3 1/6] m68k: merge mmu and non-mmu versions of muldi3 gerg
2011-04-21 0:24 ` [PATCH v3 2/6] m68k: merge mmu and non-mmu versions of lib/Makefile gerg
2011-04-21 0:24 ` [PATCH v3 3/6] m68k: remove duplicate memmove() implementation gerg
2011-04-21 0:24 ` [PATCH v3 4/6] m68k: remove duplicate memset() implementation gerg
2011-04-21 0:24 ` [PATCH v3 5/6] m68k: remove duplicate memcpy() implementation gerg
2011-04-21 0:24 ` [PATCH v3 6/6] m68k: let Makefile sort out compiling mmu and non-mmu lib/checksum.c gerg
2011-05-23 19:26 ` [PATCH v3 5/6] m68k: remove duplicate memcpy() implementation Geert Uytterhoeven
2011-05-23 19:54 ` Andreas Schwab
2011-05-23 23:55 ` Greg Ungerer
2011-05-24 7:34 ` Andreas Schwab [this message]
2011-05-24 7:51 ` Geert Uytterhoeven
2011-05-24 8:06 ` Andreas Schwab
2011-05-26 6:23 ` Greg Ungerer
2011-05-26 6:38 ` Geert Uytterhoeven
2011-06-02 5:18 ` Greg Ungerer
2011-06-02 7:43 ` Geert Uytterhoeven
2011-06-02 12:34 ` Greg Ungerer
2011-05-26 7:28 ` Gavin Lambert
2011-05-26 11:30 ` [uClinux-dev] " Greg Ungerer
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=m31uzoy2ks.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=gerg@snapgear.com \
--cc=gerg@uclinux.org \
--cc=linux-m68k@vger.kernel.org \
--cc=uclinux-dev@uclinux.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.