From: David Coulson <david@davidcoulson.net>
To: user-mode-linux-devel@lists.sourceforge.net,
Jeff Dike <jdike@addtoit.com>
Subject: [Fwd: Re: [uml-devel] uml-patch-2.4.22-4]
Date: Sat, 13 Sep 2003 23:35:35 -0400 [thread overview]
Message-ID: <3F63E207.8070607@davidcoulson.net> (raw)
+ {9, "urandom", S_IRUGO | S_IWUSR, &urandom_fops},
+ {10, "anon", S_IRUGO | S_IWUSR, &anon_fops},
That patch to mem.c is borked.
-------- Original Message --------
Subject: Re: [uml-devel] uml-patch-2.4.22-4
Date: Sat, 13 Sep 2003 23:32:38 -0400
From: David Coulson <david@davidcoulson.net>
To: Jeff Dike <jdike@addtoit.com>
References: <200309140317.h8E3H2e4008178@ccure.karaya.com>
Jeff Dike wrote:
> There are also a couple of cleanups from Stian, and also from me, since I
> was feeling left out of all the fun.
If I compile 2.4.22-4um without CONFIG_DEV_ANON, I get this:
mem.c: In function `memory_devfs_register':
mem.c:728: error: `anon_fops' undeclared (first use in this function)
mem.c:728: error: (Each undeclared identifier is reported only once
mem.c:728: error: for each function it appears in.)
mem.c:728: error: initializer element is not constant
mem.c:728: error: (near initialization for `list[8].fops')
mem.c:728: error: initializer element is not constant
mem.c:728: error: (near initialization for `list[8]')
What is CONFIG_DEV_ANON and why would I want it?
David
--
David Coulson email: d@vidcoulson.com
Linux Developer / web: http://davidcoulson.net/
Network Engineer phone: (216) 533-6967
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
reply other threads:[~2003-09-14 3:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3F63E207.8070607@davidcoulson.net \
--to=david@davidcoulson.net \
--cc=jdike@addtoit.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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).