From: Jeff Dike <jdike@addtoit.com>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] potentially dead CONFIG variables under arch/um
Date: Tue, 17 Jul 2007 11:55:55 -0400 [thread overview]
Message-ID: <20070717155555.GA7965@c2.user-mode-linux.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0707170723170.21802@localhost.localdomain>
Oops, sorry for ignoring your last post...
On Tue, Jul 17, 2007 at 07:24:09AM -0400, Robert P. J. Day wrote:
>
> ========== HARDDOG_NOWAYOUT ==========
> arch/um/drivers/harddog_kern.c:72:#ifdef CONFIG_HARDDOG_NOWAYOUT
This looks bogus. There is a WATCHDOG_NOWAYOUT and I think we should
use that instead.
> ========== PROC_MM ==========
> arch/um/kernel/ptrace.c:13:#ifdef CONFIG_PROC_MM
> arch/um/kernel/ptrace.c:227:#ifdef CONFIG_PROC_MM
> ========== TTY_LOG ==========
> arch/um/os-Linux/Makefile:15:obj-$(CONFIG_TTY_LOG) += tty_log.o
> arch/um/os-Linux/Makefile:16:user-objs-$(CONFIG_TTY_LOG) += tty_log.o
> arch/um/kernel/exec.c:34:#ifdef CONFIG_TTY_LOG
> arch/um/kernel/exec.c:42:#ifdef CONFIG_TTY_LOG
These two are used, but in code which is not yet merged. These
references leaked into mainline by accident.
Jeff
--
Work email - jdike at linux dot intel dot com
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
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:[~2007-07-17 15:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-17 11:24 [uml-devel] potentially dead CONFIG variables under arch/um Robert P. J. Day
2007-07-17 15:55 ` Jeff Dike [this message]
2007-07-17 16:04 ` Robert P. J. Day
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=20070717155555.GA7965@c2.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=rpjday@mindspring.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 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.