public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Albert Cahalan <albert@users.sourceforge.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] multiple namespaces
Date: Thu, 1 Apr 2004 00:25:49 -0800	[thread overview]
Message-ID: <20040401002549.4e124592.akpm@osdl.org> (raw)
In-Reply-To: <1080800087.1490.14.camel@cube>

Albert Cahalan <albert@users.sourceforge.net> wrote:
>
>  This patch lets a task have access to multiple namespaces.
>  You can create extra namespaces with the included SUBST command.
>  Then, from the bash prompt, you can switch from one namespace
>  to another by typing commands like "C" or "D". The default
>  namespace is "C" for compatibility reasons.

Applied, thanks.   But you missed this bit:


 25-akpm/kernel/printk.c |    9 ++++++++-
 1 files changed, 8 insertions(+), 1 deletion(-)

diff -puN kernel/printk.c~a kernel/printk.c
--- 25/kernel/printk.c~a	2004-04-01 00:24:07.036691080 -0800
+++ 25-akpm/kernel/printk.c	2004-04-01 00:24:41.266487360 -0800
@@ -459,7 +459,7 @@ static void call_console_drivers(unsigne
 	_call_console_drivers(start_print, end, msg_level);
 }
 
-static void emit_log_char(char c)
+static void __emit_log_char(char c)
 {
 	LOG_BUF(log_end) = c;
 	log_end++;
@@ -471,6 +471,13 @@ static void emit_log_char(char c)
 		logged_chars++;
 }
 
+static void emit_log_char(char c)
+{
+	if (c == '\n')
+		__emit_log_char('\r');
+	__emit_log_char(c);
+}
+
 /*
  * This is printk.  It can be called from any context.  We want it to work.
  * 

_


  parent reply	other threads:[~2004-04-01  8:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-01  6:14 [PATCH] multiple namespaces Albert Cahalan
2004-04-01  6:50 ` bert hubert
2004-04-01  7:36 ` Cory Tusar
2004-04-01  8:24   ` Nick Piggin
2004-04-01  8:25 ` Andrew Morton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-04-01  6:11 Albert Cahalan

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=20040401002549.4e124592.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=albert@users.sourceforge.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox