From: Christoph Hellwig <hch@lst.de>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: hch@lst.de, akpm@linux-foundation.org, dan.j.williams@intel.com,
daniel@ffwll.ch, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-nvdimm@lists.01.org,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
clang-built-linux@googlegroups.com
Subject: Re: [PATCH 2/2] mm: simplify follow_pte{,pmd}
Date: Wed, 11 Nov 2020 09:18:00 +0100 [thread overview]
Message-ID: <20201111081800.GA23492@lst.de> (raw)
In-Reply-To: <20201111022122.1039505-1-ndesaulniers@google.com>
On Tue, Nov 10, 2020 at 06:21:22PM -0800, Nick Desaulniers wrote:
> Sorry, I think this patch may be causing a regression for us for s390?
> https://travis-ci.com/github/ClangBuiltLinux/continuous-integration/jobs/432129279#L768
>
> (via https://lore.kernel.org/linux-mm/20201029101432.47011-3-hch@lst.de)
Hmm, the call to follow_pte_pmd in the s390 code does not actually exist
in my tree.
next prev parent reply other threads:[~2020-11-11 8:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 10:14 simplify follow_pte a bit Christoph Hellwig
2020-10-29 10:14 ` [PATCH 1/2] mm: unexport follow_pte_pmd Christoph Hellwig
2020-11-10 18:32 ` Matthew Wilcox
2020-10-29 10:14 ` [PATCH 2/2] mm: simplify follow_pte{,pmd} Christoph Hellwig
2020-11-10 18:42 ` Matthew Wilcox
2020-11-11 2:21 ` Nick Desaulniers
2020-11-11 8:18 ` Christoph Hellwig [this message]
2020-11-11 8:26 ` Christian Borntraeger
2020-11-11 8:28 ` Christoph Hellwig
2020-11-11 11:12 ` Stephen Rothwell
2020-11-10 18:26 ` simplify follow_pte a bit Christoph Hellwig
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=20201111081800.GA23492@lst.de \
--to=hch@lst.de \
--cc=akpm@linux-foundation.org \
--cc=borntraeger@de.ibm.com \
--cc=clang-built-linux@googlegroups.com \
--cc=dan.j.williams@intel.com \
--cc=daniel@ffwll.ch \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@lists.01.org \
--cc=ndesaulniers@google.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;
as well as URLs for NNTP newsgroup(s).