From: Jeff Dike <jdike@addtoit.com>
To: blaisorblade@yahoo.it
Cc: linux-kernel@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [patch 1/3] uml: share page bits handling between 2 and 3 level pagetables
Date: Sat, 30 Jul 2005 12:02:18 -0400 [thread overview]
Message-ID: <20050730160218.GB4585@ccure.user-mode-linux.org> (raw)
In-Reply-To: <20050728185655.9C6ADA3@zion.home.lan>
On Thu, Jul 28, 2005 at 08:56:53PM +0200, blaisorblade@yahoo.it wrote:
> As obvious, a "core code nice cleanup" is not a "stability-friendly patch" so
> usual care applies.
These look reasonable, as they are what we discussed in Ottawa.
I'll put them in my tree and see if I see any problems. I would
suggest sending these in early after 2.6.13 if they seem OK.
Jeff
next prev parent reply other threads:[~2005-07-30 17:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-28 18:56 [patch 1/3] uml: share page bits handling between 2 and 3 level pagetables blaisorblade
2005-07-30 16:02 ` Jeff Dike [this message]
2005-07-30 18:54 ` Blaisorblade
2005-08-10 19:37 ` Blaisorblade
2005-08-12 17:05 ` Jeff Dike
2005-09-02 20:17 ` Jeff Dike
2005-09-03 5:08 ` Hugh Dickins
2005-09-04 11:33 ` [uml-devel] " Blaisorblade
2005-08-12 18:37 ` 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=20050730160218.GB4585@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=blaisorblade@yahoo.it \
--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