From: Roman Zippel <zippel@linux-m68k.org>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: linux-m68k@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 09/36] m68k: fix macro syntax to make current binutils happy
Date: Mon, 26 Dec 2005 22:59:18 +0100 [thread overview]
Message-ID: <200512262259.19230.zippel@linux-m68k.org> (raw)
In-Reply-To: <E1EpIOj-0004qc-HA@ZenIV.linux.org.uk>
Hi,
On Thursday 22 December 2005 05:49, Al Viro wrote:
> recent as(1) doesn't think that . terminates a macro name, so
> getuser.l is _not_ treated as invoking getuser with .l as the
> first argument.
Could you please hold back with the binutils changes? Eventually this should
rather be fixed in gas or they have to properly document the expected
behaviour, so it doesn't break the next time they change it.
bye, Roman
next prev parent reply other threads:[~2005-12-26 22:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-22 4:49 [PATCH 09/36] m68k: fix macro syntax to make current binutils happy Al Viro
2005-12-26 21:59 ` Roman Zippel [this message]
2005-12-29 21:03 ` Al Viro
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=200512262259.19230.zippel@linux-m68k.org \
--to=zippel@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=viro@ftp.linux.org.uk \
/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