All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ftp.linux.org.uk>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org,
	linux-m68k@vger.kernel.org
Subject: Re: [PATCH 08/41] m68k: fix macro syntax to make current binutils happy
Date: Thu, 5 Jan 2006 11:37:08 +0000	[thread overview]
Message-ID: <20060105113708.GT27946@ftp.linux.org.uk> (raw)
In-Reply-To: <20060105035118.GS27946@ftp.linux.org.uk>

On Thu, Jan 05, 2006 at 03:51:18AM +0000, Al Viro wrote:
> On Thu, Jan 05, 2006 at 04:11:35AM +0100, Roman Zippel wrote:
> > Hi,
> > 
> > On Wednesday 04 January 2006 00:27, 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.
> > 
> > Al, please don't send the binutils patches yet, I simply need more time to 
> > figure out how to deal with it and it's not a critical patch.
> > Linus, please don't apply patch 8 and 9.
> 
> OK.  Nothing else depends on those; however, getuser.l stuff _is_ documented.
> 
> Frankly, my preference long-term would be to kill the .macro and just
> use C preprocessor for expansion.  Do you have any objections against
> such variant?

Scratch that; too much PITA to implement the horrors you've got there
(vararg recursive macros <shudder>).

Al, very tempted to do scripts/m4/ - would far more compact than e.g. kconfig,
if we don't bother with GNU extensions; classic m4 is essentially a weekend
project...

  reply	other threads:[~2006-01-05 11:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-03 23:27 [PATCH 08/41] m68k: fix macro syntax to make current binutils happy Al Viro
2006-01-05  3:11 ` Roman Zippel
2006-01-05  3:51   ` Al Viro
2006-01-05 11:37     ` Al Viro [this message]
2006-01-08 17:11       ` Roman Zippel

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=20060105113708.GT27946@ftp.linux.org.uk \
    --to=viro@ftp.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=torvalds@osdl.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 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.