From: Jon Smirl <jonsmirl@gmail.com>
To: "viro@parcelfarce.linux.theplanet.co.uk"
<viro@parcelfarce.linux.theplanet.co.uk>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: __initcall macros and C token pasting
Date: Sat, 25 Sep 2004 14:40:00 -0400 [thread overview]
Message-ID: <9e4733910409251140569fdd36@mail.gmail.com> (raw)
In-Reply-To: <20040925183234.GU23987@parcelfarce.linux.theplanet.co.uk>
Sorry for bothering you. I'm trying to work out a scheme for
transitioning most of the DRM() macros out of the DRM source without
breaking everything. Right now I can get rid of all but six uses. I
was going to fix this one in the next pass and I needed a solution to
keep everything working for the moment. I was focused on the point of
the error and didn't think about fixing it at a higher level.
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2004-09-25 18:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-25 17:57 __initcall macros and C token pasting Jon Smirl
2004-09-25 18:32 ` viro
2004-09-25 18:40 ` Jon Smirl [this message]
2004-09-25 19:17 ` Jon Smirl
2004-09-26 17:21 ` Olivier Galibert
2004-09-26 17:24 ` Tonnerre
2004-09-26 17:42 ` Christoph Hellwig
2004-09-26 19:56 ` Geert Uytterhoeven
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=9e4733910409251140569fdd36@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@parcelfarce.linux.theplanet.co.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