From: Antoine Martin <antoine@nagafix.co.uk>
To: Jeff Dike <jdike@addtoit.com>
Cc: Blaisorblade <blaisorblade@yahoo.it>,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Re: TLS support - status - need for re-testing
Date: Fri, 24 Mar 2006 10:39:59 +0000 [thread overview]
Message-ID: <1143196799.2868.1.camel@localhost> (raw)
In-Reply-To: <20060324015120.GA8104@ccure.user-mode-linux.org>
[-- Attachment #1: Type: text/plain, Size: 938 bytes --]
On Thu, 2006-03-23 at 20:51 -0500, Jeff Dike wrote:
> On Fri, Mar 24, 2006 at 12:44:05AM +0100, Blaisorblade wrote:
> > Yes, that is true, but meanwhile give a testing to them, especially regressio
> > test the new patches. I can't merge new patches in until I'm sure they don't
> > cause regressions.
>
> OK, I give it a thumbs-up on a first boot - it's running my FC5
> filesystem without any trouble. I'll keep playing with it and let you
> know of any trouble.
I haven't been able to run FC4/FC5 x86 filesystems with any of the
patches floating around. (on amd64 host)
> Attached is a tarball of the patches merged after the patches I have
> planned for 2.6.17. Nothing major, just some fuzz, some Makefile
> rejections, and rejections from some whitespace cleanup in
> kernel/skas/process_kern.c.
I couldn't figure out in which order I need to apply these (no series
file) and I've ran out of time.
Antoine
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 191 bytes --]
next prev parent reply other threads:[~2006-03-24 10:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-23 2:17 [uml-devel] TLS support - status - need for re-testing Blaisorblade
2006-03-23 11:29 ` [uml-devel] " Antoine Martin
2006-03-23 21:14 ` Jeff Dike
2006-03-23 23:44 ` Blaisorblade
2006-03-24 1:51 ` Jeff Dike
2006-03-24 10:39 ` Antoine Martin [this message]
2006-03-24 11:44 ` Blaisorblade
2006-03-24 11:43 ` Blaisorblade
2006-03-24 4:17 ` Jeff Dike
2006-03-24 11:43 ` Blaisorblade
2006-03-24 17:32 ` Jeff Dike
2006-03-24 18:44 ` Blaisorblade
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=1143196799.2868.1.camel@localhost \
--to=antoine@nagafix.co.uk \
--cc=blaisorblade@yahoo.it \
--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 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.