From: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] mm/page_ext: Trivial cleanups
Date: Mon, 11 Jun 2018 17:34:15 +0300 [thread overview]
Message-ID: <20180611143414.vqbfvrn2bvqtjpfw@black.fi.intel.com> (raw)
In-Reply-To: <20180531135457.20167-1-kirill.shutemov@linux.intel.com>
On Thu, May 31, 2018 at 01:54:55PM +0000, Kirill A. Shutemov wrote:
> A pair of trivial cleanups in preparation for memory encryption.
Andrew, can we get these applied?
--
Kirill A. Shutemov
next prev parent reply other threads:[~2018-06-11 14:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-31 13:54 Kirill A. Shutemov
2018-05-31 13:54 ` [PATCH 1/2] mm/page_ext: Drop definition of unused PAGE_EXT_DEBUG_POISON Kirill A. Shutemov
2018-05-31 13:54 ` [PATCH 2/2] mm/page_ext: Constify lookup_page_ext() argument Kirill A. Shutemov
2018-06-11 14:34 ` Kirill A. Shutemov [this message]
2018-06-11 22:47 ` [PATCH 0/2] mm/page_ext: Trivial cleanups Andrew Morton
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=20180611143414.vqbfvrn2bvqtjpfw@black.fi.intel.com \
--to=kirill.shutemov@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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