From: "David S. Miller" <davem@redhat.com>
To: chas3@users.sourceforge.net
Cc: chas@cmf.nrl.navy.mil, netdev@oss.sgi.com, huisheng@angelfire.com
Subject: Re: [PATCH][ATM]: prevent user-space compilation errors
Date: Wed, 11 Feb 2004 22:02:32 -0800 [thread overview]
Message-ID: <20040211220232.7f54babc.davem@redhat.com> (raw)
In-Reply-To: <200402111425.i1BEPtRr005772@ginger.cmf.nrl.navy.mil>
On Wed, 11 Feb 2004 09:25:57 -0500
chas williams (contractor) <chas@cmf.nrl.navy.mil> wrote:
> the script used by redhat to generate glibc-kernheaders doesnt
> seem to handle #ifdef __KERNEL__/#else/#endif properly. it seems
> to remove the #ifdef/#else and leaves a dangling #endif.
>
> this patch simplifies things a bit. please apply to 2.6 and 2.4.
Applied, thanks Chas.
prev parent reply other threads:[~2004-02-12 6:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-11 14:25 [PATCH][ATM]: prevent user-space compilation errors chas williams
2004-02-12 6:02 ` David S. Miller [this message]
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=20040211220232.7f54babc.davem@redhat.com \
--to=davem@redhat.com \
--cc=chas3@users.sourceforge.net \
--cc=chas@cmf.nrl.navy.mil \
--cc=huisheng@angelfire.com \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).