From: Al Viro <viro@ftp.linux.org.uk>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: linux-m68k@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] m68k: more workarounds for recent binutils idiocy
Date: Thu, 12 Oct 2006 01:50:58 +0100 [thread overview]
Message-ID: <20061012005058.GG29920@ftp.linux.org.uk> (raw)
In-Reply-To: <20061011220726.GE29920@ftp.linux.org.uk>
On Wed, Oct 11, 2006 at 11:07:26PM +0100, Al Viro wrote:
> OK... Would be nice to find out which versions are broken (that's
> Documentation/Changes fodder), I'll see to it.
2.16.91.0.[3-6] are to be avoided on m68k.
> What about the first problem? Even current binutils CVS treats
> foo.bar as a single identifier, and doesn't recognize it as invocation
> of foo with .bar as the first argument. Any objections against the
> first patch?
next prev parent reply other threads:[~2006-10-12 0:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 21:13 [PATCH 2/2] m68k: more workarounds for recent binutils idiocy Al Viro
2006-10-11 21:30 ` Roman Zippel
2006-10-11 22:07 ` Al Viro
2006-10-12 0:50 ` Al Viro [this message]
2006-10-11 22:12 ` Andreas Schwab
2006-10-12 0:49 ` Al Viro
2006-10-12 2:24 ` Dave Jones
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=20061012005058.GG29920@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=zippel@linux-m68k.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox