From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andrew Morton <akpm@linux-foundation.org>
Subject: [ofa-general] Re: [PATCH 01 of 11] mmu-notifier-core
Date: Wed, 7 May 2008 13:05:28 -0700
Message-ID: <20080507130528.adfd154c.akpm@linux-foundation.org>
References: <patchbomb.1210170950@duo.random>
	<e20917dcc8284b6a07cf.1210170951@duo.random>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: npiggin@suse.de, chrisw@redhat.com, rusty@rustcorp.com.au,
	a.p.zijlstra@chello.nl, kvm-devel@lists.sourceforge.net,
	kanojsarcar@yahoo.com, rdreier@cisco.com, steiner@sgi.com,
	linux-kernel@vger.kernel.org, avi@qumranet.com,
	aliguori@us.ibm.com, paulmck@us.ibm.com, linux-mm@kvack.org,
	holt@sgi.com, general@lists.openfabrics.org, hugh@veritas.com,
	marcelo@kvack.org, dada1@cosmosbay.com,
	Linus Torvalds <torvalds@linux-foundation.org>, clameter@sgi.com
To: Andrea Arcangeli <andrea@qumranet.com>
Return-path: <general-bounces@lists.openfabrics.org>
In-Reply-To: <e20917dcc8284b6a07cf.1210170951@duo.random>
List-Unsubscribe: <http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general>,
	<mailto:general-request@lists.openfabrics.org?subject=unsubscribe>
List-Archive: <http://lists.openfabrics.org/pipermail/general>
List-Post: <mailto:general@lists.openfabrics.org>
List-Help: <mailto:general-request@lists.openfabrics.org?subject=help>
List-Subscribe: <http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general>,
	<mailto:general-request@lists.openfabrics.org?subject=subscribe>
Sender: general-bounces@lists.openfabrics.org
Errors-To: general-bounces@lists.openfabrics.org
List-Id: kvm.vger.kernel.org

On Wed, 07 May 2008 16:35:51 +0200
Andrea Arcangeli <andrea@qumranet.com> wrote:

> # HG changeset patch
> # User Andrea Arcangeli <andrea@qumranet.com>
> # Date 1210096013 -7200
> # Node ID e20917dcc8284b6a07cfcced13dda4cbca850a9c
> # Parent  5026689a3bc323a26d33ad882c34c4c9c9a3ecd8
> mmu-notifier-core

The patch looks OK to me.

The proposal is that we sneak this into 2.6.26.  Are there any
sufficiently-serious objections to this?

The patch will be a no-op for 2.6.26.

This is all rather unusual.  For the record, could we please review the
reasons for wanting to do this?

Thanks.