From: Mark Vitale <mvitale@sinenomine.net>
To: "linux-mm@kvack.org" <linux-mm@kvack.org>
Cc: Dan Williams <dan.j.williams@intel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Joe Gorse <jgorse@sinenomine.net>,
"release-team@openafs.org" <release-team@openafs.org>
Subject: re: [PATCH v4 0/8] mm: Rework hmm to use devm_memremap_pages and other fixes
Date: Fri, 20 Jul 2018 14:43:14 +0000 [thread overview]
Message-ID: <37267986-A987-4AD7-96CE-C1D2F116A4AC@sinenomine.net> (raw)
On Jul 11, 2018, Dan Williams wrote:
> Changes since v3 [1]:
> * Collect Logan's reviewed-by on patch 3
> * Collect John's and Joe's tested-by on patch 8
> * Update the changelog for patch 1 and 7 to better explain the
> EXPORT_SYMBOL_GPL rationale.
> * Update the changelog for patch 2 to clarify that it is a cleanup to
> make the following patch-3 fix easier
>
> [1]: https://lkml.org/lkml/2018/6/19/108
>
> ---
>
> Hi Andrew,
>
> As requested, here is a resend of the devm_memremap_pages() fixups.
> Please consider for 4.18.
What is the status of this patchset? OpenAFS is unable to build on
Linux 4.18 without the last patch in this set:
8/8 mm: Fix exports that inadvertently make put_page() EXPORT_SYMBOL_GPL
Will this be merged soon to linux-next, and ultimately to a Linux 4.18 rc?
Thank you,
--
Mark Vitale
mvitale@sinenomine.net
on behalf of the OpenAFS release team
next reply other threads:[~2018-07-20 14:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 14:43 Mark Vitale [this message]
2018-07-20 19:51 ` Andrew Morton
2018-07-20 19:57 ` Jerome Glisse
2018-07-20 20:01 ` Matthew Wilcox
2018-07-20 20:17 ` Jerome Glisse
2018-07-21 16:11 ` Dan Williams
-- strict thread matches above, loose matches on Subject: below --
2018-07-11 5:14 Dan Williams
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=37267986-A987-4AD7-96CE-C1D2F116A4AC@sinenomine.net \
--to=mvitale@sinenomine.net \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.org \
--cc=jgorse@sinenomine.net \
--cc=linux-mm@kvack.org \
--cc=release-team@openafs.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