From: Gerd Knorr <kraxel@bytesex.org>
To: Blaisorblade <blaisorblade_spam@yahoo.it>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, jdike@addtoit.com,
bstroesser@fujitsu-siemens.com,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: VFS interactions with UML and other big UML changes (was: Re: [patch 1/2] Uml - first part rework of run_helper() and users.)
Date: Wed, 1 Dec 2004 10:02:03 +0100 [thread overview]
Message-ID: <20041201090203.GD12963@bytesex> (raw)
In-Reply-To: <200412010120.39579.blaisorblade_spam@yahoo.it>
> > uml-terminal-cleanup.patch
>
> I don't know technically this one. It won't probably go in 2.6.10, I think
> later... tested in the SuSE tree, but let's be quiet in merging _big_ things,
> ok? It was also tested in a different tree, so it perfectly working on 2.6.9
> does not mean perfectly working on current kernels.
Tested by me on 2.6.10-rc2-bk<something> as well. It needed some
trivial adaptions to the tty layer changes done by Linus compared
to the old 2.6.9 version. I'm pretty confident it wouldn't break
anything, but as it is to big to be classified as ObviouslyCorrect[tm]
fix it probably should not go to into 2.6.10 but be merged in the
2.6.11 cycle.
Gerd
--
#define printk(args...) fprintf(stderr, ## args)
prev parent reply other threads:[~2004-12-01 9:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20041130200845.2C5058BAFE@zion.localdomain>
[not found] ` <20041130152017.129e134c.akpm@osdl.org>
2004-12-01 0:20 ` VFS interactions with UML and other big UML changes (was: Re: [patch 1/2] Uml - first part rework of run_helper() and users.) Blaisorblade
2004-12-01 0:33 ` Andrew Morton
2004-12-01 0:51 ` [uml-devel] " Blaisorblade
2004-12-01 9:02 ` Gerd Knorr [this message]
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=20041201090203.GD12963@bytesex \
--to=kraxel@bytesex.org \
--cc=akpm@osdl.org \
--cc=blaisorblade_spam@yahoo.it \
--cc=bstroesser@fujitsu-siemens.com \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--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