From: Bjorn Helgaas <helgaas@kernel.org>
To: Logan Gunthorpe <logang@deltatee.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux MM <linux-mm@kvack.org>,
linux-pci@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Dan Williams <dan.j.williams@intel.com>
Subject: Re: [PATCH] PCI/P2PDMA: Match interface changes to devm_memremap_pages()
Date: Tue, 11 Dec 2018 07:56:26 -0600 [thread overview]
Message-ID: <20181211135626.GC99796@google.com> (raw)
In-Reply-To: <c226426d-e88c-da18-f643-f3faaf1c0dbd@deltatee.com>
On Thu, Dec 06, 2018 at 03:17:00PM -0700, Logan Gunthorpe wrote:
>
>
> On 2018-12-06 1:46 p.m., Bjorn Helgaas wrote:
> > On Fri, Nov 30, 2018 at 03:59:11PM -0700, Logan Gunthorpe wrote:
> >> "mm-hmm-mark-hmm_devmem_add-add_resource-export_symbol_gpl.patch" in the
> >> mm tree breaks p2pdma. The patch was written and reviewed before p2pdma
> >> was merged so the necessary changes were not done to the call site in
> >> that code.
> >>
> >> Without this patch, all drivers will fail to register P2P resources
> >> because devm_memremap_pages() will return -EINVAL due to the 'kill'
> >> member of the pagemap structure not yet being set.
> >>
> >> Signed-off-by: Logan Gunthorpe <logang@deltatee.com>
> >> Cc: Andrew Morton <akpm@linux-foundation.org>
> >> Cc: Dan Williams <dan.j.williams@intel.com>
> >> Cc: Bjorn Helgaas <bhelgaas@google.com>
> >
> > Applied with Dan's reviewed-by to pci/peer-to-peer for v4.21, thanks!
> >
> > If the mm patch you mention gets merged for v4.20, let me know and I can
> > promote this to for-linus so v4.20 doesn't end up broken.
>
> Thanks Bjorn, but I think Andrew has also picked it up in the mm tree
> with the patch in question. My hope is that he squashes the two but I'm
> not sure what his intentions are. I mostly copied you for information
> purposes as this patch shouldn't even compile without Dan's patch.
>
> Though, I guess we'll find out what goes in after the merge window --
> you may not need to do anything.
OK, I dropped this because I don't have the matching mm patch. I agree,
it should be squashed so we avoid a bisection hole. Let me know if I
need to do anything else with this.
Bjorn
prev parent reply other threads:[~2018-12-11 13:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 22:59 Logan Gunthorpe
2018-12-01 0:52 ` Dan Williams
2018-12-06 20:46 ` Bjorn Helgaas
2018-12-06 22:17 ` Logan Gunthorpe
2018-12-11 13:56 ` Bjorn Helgaas [this message]
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=20181211135626.GC99796@google.com \
--to=helgaas@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-pci@vger.kernel.org \
--cc=logang@deltatee.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox