LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Andrew Morton <email@example.com>
To: Jason Gunthorpe <firstname.lastname@example.org>
Cc: Christoph Hellwig <email@example.com>,
Mark Rutland <firstname.lastname@example.org>,
Robin Murphy <email@example.com>,
Michal Hocko <firstname.lastname@example.org>
Subject: Re: [PATCH v3 0/4] Devmap cleanups + arm64 support
Date: Wed, 26 Jun 2019 20:35:51 -0700 [thread overview]
Message-ID: <email@example.com> (raw)
On Wed, 26 Jun 2019 15:45:47 +0000 Jason Gunthorpe <firstname.lastname@example.org> wrote:
> On Wed, Jun 26, 2019 at 08:38:29AM -0700, Christoph Hellwig wrote:
> > On Wed, Jun 26, 2019 at 01:31:40PM +0100, Mark Rutland wrote:
> > > On Wed, Jun 26, 2019 at 12:35:33AM -0700, Christoph Hellwig wrote:
> > > > Robin, Andrew:
> > >
> > > As a heads-up, Robin is currently on holiday, so this is all down to
> > > Andrew's preference.
> > >
> > > > I have a series for the hmm tree, which touches the section size
> > > > bits, and remove device public memory support.
> > > >
> > > > It might be best if we include this series in the hmm tree as well
> > > > to avoid conflicts. Is it ok to include the rebase version of at least
> > > > the cleanup part (which looks like it is not required for the actual
> > > > arm64 support) in the hmm tree to avoid conflicts?
> > >
> > > Per the cover letter, the arm64 patch has a build dependency on the
> > > others, so that might require a stable brnach for the common prefix.
> > I guess we'll just have to live with the merge errors then, as the
> > mm tree is a patch series and thus can't easily use a stable base
> > tree. That is unlike Andrew wants to pull in the hmm tree as a prep
> > patch for the series.
> It looks like the first three patches apply cleanly to hmm.git ..
> So what we can do is base this 4 patch series off rc6 and pull the
> first 3 into hmm and the full 4 into arm.git. We use this workflow often
> with rdma and netdev.
> Let me know and I can help orchestate this.
Well. Whatever works. In this situation I'd stage the patches after
linux-next and would merge them up after the prereq patches have been
merged into mainline. Easy.
next prev parent reply other threads:[~2019-06-27 3:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 15:03 Robin Murphy
2019-05-23 15:03 ` [PATCH v3 1/4] mm/memremap: Rename and consolidate SECTION_SIZE Robin Murphy
2019-05-23 15:03 ` [PATCH v3 2/4] mm: clean up is_device_*_page() definitions Robin Murphy
2019-05-23 15:03 ` [PATCH v3 3/4] mm: introduce ARCH_HAS_PTE_DEVMAP Robin Murphy
2019-05-23 15:03 ` [PATCH v3 4/4] arm64: mm: Implement pte_devmap support Robin Murphy
2019-05-24 18:08 ` Will Deacon
2019-05-24 18:38 ` Robin Murphy
2019-05-27 6:23 ` Anshuman Khandual
2019-05-28 13:46 ` [PATCH v3.1 " Robin Murphy
2019-05-29 10:03 ` Will Deacon
2019-06-26 7:35 ` [PATCH v3 0/4] Devmap cleanups + arm64 support Christoph Hellwig
2019-06-26 12:31 ` Mark Rutland
2019-06-26 15:38 ` Christoph Hellwig
2019-06-26 15:45 ` Jason Gunthorpe
2019-06-27 3:35 ` Andrew Morton [this message]
2019-07-04 18:53 ` Andrew Morton
2019-07-04 19:59 ` Jason Gunthorpe
2019-07-04 20:53 ` Andrew Morton
2019-07-04 21:28 ` Jason Gunthorpe
2019-07-05 15:47 ` Jason Gunthorpe
2019-07-04 20:54 ` Robin Murphy
2019-07-04 21:13 ` Andrew Morton
2019-07-05 11:16 ` Robin Murphy
2019-07-04 23:37 ` Dan Williams
2019-07-05 12:32 ` Jason Gunthorpe
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--subject='Re: [PATCH v3 0/4] Devmap cleanups + arm64 support' \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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).