All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: Andrew Morton <akpm@osdl.org>,
	LKML <linux-kernel@vger.kernel.org>,
	uml-devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: [uml-devel] [PATCH 0/2] UML - Two fixes for 2.6.26
Date: Thu, 12 Jun 2008 12:28:41 -0400	[thread overview]
Message-ID: <20080612162841.GA8402@c2.user-mode-linux.org> (raw)

Here are a couple small, but important fixes for 2.6.26.  One is a
compilation problem that I added recently, and the other is a fix for
UML crashing needlessly when the host's PTRACE_SYSEMU is broken.

    	     		     Jeff

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

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

WARNING: multiple messages have this Message-ID (diff)
From: Jeff Dike <jdike@addtoit.com>
To: Andrew Morton <akpm@osdl.org>,
	LKML <linux-kernel@vger.kernel.org>,
	uml-devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: [PATCH 0/2] UML - Two fixes for 2.6.26
Date: Thu, 12 Jun 2008 12:28:41 -0400	[thread overview]
Message-ID: <20080612162841.GA8402@c2.user-mode-linux.org> (raw)

Here are a couple small, but important fixes for 2.6.26.  One is a
compilation problem that I added recently, and the other is a fix for
UML crashing needlessly when the host's PTRACE_SYSEMU is broken.

    	     		     Jeff

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

             reply	other threads:[~2008-06-12 16:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-12 16:28 Jeff Dike [this message]
2008-06-12 16:28 ` [PATCH 0/2] UML - Two fixes for 2.6.26 Jeff Dike

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=20080612162841.GA8402@c2.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --cc=akpm@osdl.org \
    --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 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.