linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Joe Perches <joe@perches.com>
Cc: Michal Hocko <mhocko@kernel.org>,
	linux-mm@kvack.org, Vlastimil Babka <vbabka@suse.cz>,
	David Rientjes <rientjes@google.com>,
	Mel Gorman <mgorman@suse.de>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Anatoly Stepanov <astepanov@cloudlinux.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Mike Snitzer <snitzer@redhat.com>,
	dm-devel@redhat.com, "Michael S. Tsirkin" <mst@redhat.com>,
	Theodore Ts'o <tytso@mit.edu>,
	kvm@vger.kernel.org, linux-ext4@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net,
	linux-security-module@vger.kernel.org,
	Dave Chinner <david@fromorbit.com>,
	Al Viro <viro@zeniv.linux.org.uk>,
	Mikulas Patocka <mpatocka@redhat.com>
Subject: Re: [RFC PATCH] mm: introduce kv[mz]alloc helpers
Date: Tue, 20 Dec 2016 14:13:41 -0800	[thread overview]
Message-ID: <20161220141341.de8b22fd66ea9bc6c4fcf962@linux-foundation.org> (raw)
In-Reply-To: <1482255502.1984.21.camel@perches.com>

On Tue, 20 Dec 2016 09:38:22 -0800 Joe Perches <joe@perches.com> wrote:

> > So what are we going to do about this patch?
> 
> Well if Andrew doesn't object again, it should probably be applied.
> Unless his silence here acts like a pocket-veto.
> 
> Andrew?  Anything to add?

I guess we should give in to reality and do this, or something like it.
But Al said he was going to dig out some patches for us to consider?


--
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>

  reply	other threads:[~2016-12-20 22:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-08 10:33 [RFC PATCH] mm: introduce kv[mz]alloc helpers Michal Hocko
2016-12-08 13:00 ` David Hildenbrand
2016-12-08 13:51   ` Michal Hocko
2016-12-09  1:44 ` Dave Chinner
2016-12-09  2:00   ` Al Viro
2016-12-09  6:22     ` Michal Hocko
2016-12-09  6:38       ` Al Viro
2016-12-09  6:51         ` Michal Hocko
2016-12-09  6:18   ` Michal Hocko
2016-12-13 10:14 ` Michal Hocko
2016-12-13 20:55   ` Andreas Dilger
2016-12-14  9:05     ` Michal Hocko
2016-12-13 22:07   ` Joe Perches
2016-12-14  8:59     ` Michal Hocko
2016-12-20 13:50       ` Michal Hocko
2016-12-20 17:38         ` Joe Perches
2016-12-20 22:13           ` Andrew Morton [this message]
     [not found]             ` <20161221065922.GB16502@dhcp22.suse.cz>
2016-12-21  8:45               ` Michal Hocko

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=20161220141341.de8b22fd66ea9bc6c4fcf962@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=astepanov@cloudlinux.com \
    --cc=david@fromorbit.com \
    --cc=dm-devel@redhat.com \
    --cc=hannes@cmpxchg.org \
    --cc=joe@perches.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mhocko@kernel.org \
    --cc=mpatocka@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=rientjes@google.com \
    --cc=snitzer@redhat.com \
    --cc=tytso@mit.edu \
    --cc=vbabka@suse.cz \
    --cc=viro@zeniv.linux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).