linux-um archives
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net,
	Antoine Martin <antoine@nagafix.co.uk>
Subject: Re: [uml-devel] Re: TLS support - status - need for re-testing
Date: Thu, 23 Mar 2006 20:51:20 -0500	[thread overview]
Message-ID: <20060324015120.GA8104@ccure.user-mode-linux.org> (raw)
In-Reply-To: <200603240044.06196.blaisorblade@yahoo.it>

[-- Attachment #1: Type: text/plain, Size: 634 bytes --]

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.

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.

				Jeff


[-- Attachment #2: tls.tar --]
[-- Type: application/x-tar, Size: 112640 bytes --]

  reply	other threads:[~2006-03-24  1:50 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 [this message]
2006-03-24 10:39       ` Antoine Martin
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=20060324015120.GA8104@ccure.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --cc=antoine@nagafix.co.uk \
    --cc=blaisorblade@yahoo.it \
    --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