All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mel Gorman <mgorman@suse.de>
To: Davidlohr Bueso <dave@stgolabs.net>
Cc: akpm@linux-foundation.org, hughd@google.com, riel@redhat.com,
	peterz@infradead.org, mingo@kernel.org,
	linux-kernel@vger.kernel.org, dbueso@suse.de, linux-mm@kvack.org
Subject: Re: [PATCH v2 -next 00/10] mm: improve usage of the i_mmap lock
Date: Mon, 10 Nov 2014 16:28:27 +0000	[thread overview]
Message-ID: <20141110162827.GA21422@suse.de> (raw)
In-Reply-To: <1414697657-1678-1-git-send-email-dave@stgolabs.net>

On Thu, Oct 30, 2014 at 12:34:07PM -0700, Davidlohr Bueso wrote:
> Changes from v1:
>  o Collected Acks from Kirill and Srikar.
>  o Updated to apply on top of linux-next.
> 

FWIW, I looked at all the patches when looking at the hugetlbfs sharing
part and while it was not a very detailed review, I also did not see
anything bad so for patches 1-7, 9 and 11

Acked-by: Mel Gorman <mgorman@suse.de>

-- 
Mel Gorman
SUSE Labs

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

WARNING: multiple messages have this Message-ID (diff)
From: Mel Gorman <mgorman@suse.de>
To: Davidlohr Bueso <dave@stgolabs.net>
Cc: akpm@linux-foundation.org, hughd@google.com, riel@redhat.com,
	peterz@infradead.org, mingo@kernel.org,
	linux-kernel@vger.kernel.org, dbueso@suse.de, linux-mm@kvack.org
Subject: Re: [PATCH v2 -next 00/10] mm: improve usage of the i_mmap lock
Date: Mon, 10 Nov 2014 16:28:27 +0000	[thread overview]
Message-ID: <20141110162827.GA21422@suse.de> (raw)
In-Reply-To: <1414697657-1678-1-git-send-email-dave@stgolabs.net>

On Thu, Oct 30, 2014 at 12:34:07PM -0700, Davidlohr Bueso wrote:
> Changes from v1:
>  o Collected Acks from Kirill and Srikar.
>  o Updated to apply on top of linux-next.
> 

FWIW, I looked at all the patches when looking at the hugetlbfs sharing
part and while it was not a very detailed review, I also did not see
anything bad so for patches 1-7, 9 and 11

Acked-by: Mel Gorman <mgorman@suse.de>

-- 
Mel Gorman
SUSE Labs

  parent reply	other threads:[~2014-11-10 16:28 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-30 19:34 [PATCH v2 -next 00/10] mm: improve usage of the i_mmap lock Davidlohr Bueso
2014-10-30 19:34 ` Davidlohr Bueso
2014-10-30 19:34 ` [PATCH 01/10] mm,fs: introduce helpers around the i_mmap_mutex Davidlohr Bueso
2014-10-30 19:34 ` [PATCH 02/10] mm: use new helper functions " Davidlohr Bueso
2014-10-30 19:34   ` Davidlohr Bueso
2014-10-30 19:34 ` [PATCH 03/10] mm: convert i_mmap_mutex to rwsem Davidlohr Bueso
2014-10-30 19:34   ` Davidlohr Bueso
2014-10-30 19:34 ` [PATCH 04/10] mm/rmap: share the i_mmap_rwsem Davidlohr Bueso
2014-10-30 19:34   ` Davidlohr Bueso
2014-10-30 19:34 ` [PATCH 05/10] uprobes: " Davidlohr Bueso
2014-10-30 19:34 ` [PATCH 06/10] mm/xip: " Davidlohr Bueso
2014-10-30 19:34 ` [PATCH 07/10] mm/memory-failure: " Davidlohr Bueso
2014-10-30 19:34 ` [PATCH 08/10] mm/mremap: " Davidlohr Bueso
2014-11-04  6:04   ` Hugh Dickins
2014-11-04  6:04     ` Hugh Dickins
2014-11-04 12:29     ` Kirill A. Shutemov
2014-11-04 12:29       ` Kirill A. Shutemov
2014-10-30 19:34 ` [PATCH 09/10] mm/nommu: " Davidlohr Bueso
2014-10-30 19:34 ` [PATCH 10/10] mm/hugetlb: " Davidlohr Bueso
2014-11-04  6:35   ` Hugh Dickins
2014-11-04  6:35     ` Hugh Dickins
2014-11-05  0:59     ` Davidlohr Bueso
2014-11-05  0:59       ` Davidlohr Bueso
2014-11-05 16:04       ` Hugh Dickins
2014-11-05 16:04         ` Hugh Dickins
2014-11-10 16:22     ` Mel Gorman
2014-11-10 16:22       ` Mel Gorman
2014-11-03  8:17 ` [PATCH v2 -next 00/10] mm: improve usage of the i_mmap lock Peter Zijlstra
2014-11-03  8:17   ` Peter Zijlstra
2014-11-10 16:28 ` Mel Gorman [this message]
2014-11-10 16:28   ` Mel Gorman

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=20141110162827.GA21422@suse.de \
    --to=mgorman@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=dave@stgolabs.net \
    --cc=dbueso@suse.de \
    --cc=hughd@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=riel@redhat.com \
    /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.