All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerome Glisse <jglisse@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Mark Vitale <mvitale@sinenomine.net>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	Dan Williams <dan.j.williams@intel.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 15:57:47 -0400	[thread overview]
Message-ID: <20180720195746.GD7697@redhat.com> (raw)
In-Reply-To: <20180720125146.02db0f40b4edc716c6f080d2@linux-foundation.org>

On Fri, Jul 20, 2018 at 12:51:46PM -0700, Andrew Morton wrote:
> On Fri, 20 Jul 2018 14:43:14 +0000 Mark Vitale <mvitale@sinenomine.net> wrote:
> 
> > 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?
> > 
> 
> Problem is, that patch is eighth in a series which we're waiting for
> Jerome to review and the changelog starts with "Now that all producers
> of dev_pagemap instances in the kernel are properly converted to
> EXPORT_SYMBOL_GPL...".

I am fine with the patchset modulo GPL, i did review it in the past
but i did not formaly reply as i was opose to the GPL changes. So my
only objection is with the GPL export, everything else looks fine.

I can review once more as it has been more than a month since i last
look at this patchset. I am working with Ben on nouveau right now so
if it breaks anything for me i will fix it once we do our final
rebase before posting.

Cheers,
Jerome

  reply	other threads:[~2018-07-20 19:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-20 14:43 [PATCH v4 0/8] mm: Rework hmm to use devm_memremap_pages and other fixes Mark Vitale
2018-07-20 19:51 ` Andrew Morton
2018-07-20 19:57   ` Jerome Glisse [this message]
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=20180720195746.GD7697@redhat.com \
    --to=jglisse@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=dan.j.williams@intel.org \
    --cc=jgorse@sinenomine.net \
    --cc=linux-mm@kvack.org \
    --cc=mvitale@sinenomine.net \
    --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 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.