From: Marcel Holtmann <marcel@holtmann.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Warning of redefined NR_OPEN
Date: Wed, 23 Feb 2005 06:00:28 +0100 [thread overview]
Message-ID: <1109134828.8506.118.camel@pegasus> (raw)
Hi,
when compiling the latest 2.6 tree from the Bitkeeper repository, I get
a lot of these:
CC init/main.o
In file included from include/linux/fs.h:202,
from include/linux/proc_fs.h:6,
from init/main.c:17:
include/linux/limits.h:4:1: warning: "NR_OPEN" redefined
In file included from include/linux/proc_fs.h:6,
from init/main.c:17:
include/linux/fs.h:24:1: warning: this is the location of the previous definition
Maybe the re-order of <linux/fs.h> to make userland happy was not a good
idea.
Regards
Marcel
next reply other threads:[~2005-02-23 5:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-23 5:00 Marcel Holtmann [this message]
2005-02-23 5:50 ` Warning of redefined NR_OPEN Chris Wright
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=1109134828.8506.118.camel@pegasus \
--to=marcel@holtmann.org \
--cc=linux-kernel@vger.kernel.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.