All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: Jason Lunz <lunz@falooley.org>
Cc: Blaisorblade <blaisorblade@yahoo.it>,
	user-mode-linux-devel@lists.sourceforge.net,
	Jens Axboe <jens.axboe@oracle.com>
Subject: Re: [uml-devel] [UML] fix crash in block layer
Date: Thu, 15 Feb 2007 12:09:16 -0500	[thread overview]
Message-ID: <20070215170916.GC5641@ccure.user-mode-linux.org> (raw)
In-Reply-To: <20070215160001.GA6774@avocado.homenet>

On Thu, Feb 15, 2007 at 11:00:01AM -0500, Jason Lunz wrote:
> Permit lvm to create logical volumes without crashing UML.

Thanks, this is in my tree.

			Jeff

-- 
Work email - jdike at linux dot intel dot com

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

       reply	other threads:[~2007-02-15 17:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070215160001.GA6774@avocado.homenet>
2007-02-15 17:09 ` Jeff Dike [this message]
2007-02-15 19:29   ` [uml-devel] [UML] fix crash in block layer Blaisorblade
2007-02-16 17:02     ` Jason Lunz
2007-02-16 18:40       ` Jeff Dike
2007-02-19 22:28         ` Blaisorblade
2007-02-16 19:10       ` Blaisorblade
2007-02-09 22:01 Jason Lunz
  -- strict thread matches above, loose matches on Subject: below --
2007-02-09 21:30 Jason Lunz

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=20070215170916.GC5641@ccure.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --cc=blaisorblade@yahoo.it \
    --cc=jens.axboe@oracle.com \
    --cc=lunz@falooley.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 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.