From: Malcolm Tredinnick <malcolm@commsecure.com.au>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] compile problem with uml-patch-2.4.22-4
Date: Mon, 15 Sep 2003 16:05:19 +1000 [thread overview]
Message-ID: <1063605919.1070.21.camel@ws14.commsecure.com.au> (raw)
In-Reply-To: <200309150545.h8F5jJWw022233@hongkong.cs.nmsu.edu>
On Mon, 2003-09-15 at 15:45, Ross Combs wrote:
> The latest 2.4 UML patch added support for an "Anonymous memory device".
> I have no idea what this is normally used for so I deselected it in the
> configuration. However that leads to a compile error in mem.c which I
> hacked around by adding #if defined(CONFIG_DEV_ANON) .. #endif around
> the last line of the array initializer:
> {10, "anon", S_IRUGO | S_IWUSR, &anon_fops}
>
> I'm not using devfs, so I'm not sure why that function is needed at all.
>
> Anyway, it seems like a small oversight and I haven't noticed any ill
> effect from the change.
Jeff mentioned this in an earlier mail to this list. It is left over
cruft from an experiment. Just leave it turned on for now. :-)
Cheers,
Malcolm
-------------------------------------------------------
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
next prev parent reply other threads:[~2003-09-15 6:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-15 5:45 [uml-devel] compile problem with uml-patch-2.4.22-4 Ross Combs
2003-09-15 6:05 ` Malcolm Tredinnick [this message]
2003-09-16 21:20 ` [uml-devel] " Patrick "Petschge" Kilian
2003-09-18 0:23 ` Jeff Dike
2003-09-18 16:36 ` Patrick "Petschge" Kilian
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=1063605919.1070.21.camel@ws14.commsecure.com.au \
--to=malcolm@commsecure.com.au \
--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