From: Jeff Dike <jdike@karaya.com>
To: torvalds@transmeta.com
Cc: linux-kernel@vger.kernel.org, jdike@karaya.com
Subject: [PATCH] UML - part 1 of 3
Date: Tue, 13 Aug 2002 12:05:47 -0500 [thread overview]
Message-ID: <200208131705.MAA02401@ccure.karaya.com> (raw)
When you reverted the stringify changes I sent last time, you missed removing
a comment, which is now grossly wrong. This patch finishes the job.
Jeff
diff -Naur orig/include/linux/stringify.h linus/include/linux/stringify.h
--- orig/include/linux/stringify.h Mon Aug 12 22:29:53 2002
+++ linus/include/linux/stringify.h Tue Aug 13 11:37:18 2002
@@ -4,10 +4,6 @@
/* Indirect stringification. Doing two levels allows the parameter to be a
* macro itself. For example, compile with -DFOO=bar, __stringify(FOO)
* converts to "bar".
- *
- * The "..." is gcc's cpp vararg macro syntax. It is required because __ALIGN,
- * in linkage.h, contains a comma, which when expanded, causes it to look
- * like two arguments, which breaks the standard non-vararg stringizer.
*/
#define __stringify_1(x) #x
next reply other threads:[~2002-08-13 15:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-13 17:05 Jeff Dike [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-03 3:40 [PATCH] UML - part 1 of 3 Jeff Dike
2002-07-28 16:33 Jeff Dike
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=200208131705.MAA02401@ccure.karaya.com \
--to=jdike@karaya.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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