linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Will Deacon <will@kernel.org>,
	 "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	 Nick Piggin <npiggin@gmail.com>, Arnd Bergmann <arnd@arndb.de>,
	 linux-arch <linux-arch@vger.kernel.org>,
	Linux-MM <linux-mm@kvack.org>,
	 Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: mainline build failure due to b67fbebd4cf9 ("mmu_gather: Force tlb-flush VM_PFNMAP vmas")
Date: Fri, 22 Jul 2022 11:57:40 -0700	[thread overview]
Message-ID: <CAHk-=whjFd-2j1qCsqdsakwcH=QML2BJBCpN2+rg10Y+PMGOOg@mail.gmail.com> (raw)
In-Reply-To: <CADVatmPkXQ3mJpdTvaHxN4qmacYBhvzz=nxduQn-y+QUz4Pu2Q@mail.gmail.com>

On Fri, Jul 22, 2022 at 10:20 AM Sudip Mukherjee
<sudipm.mukherjee@gmail.com> wrote:
>
> That fixes the alpha build failure.
> If you commit it today then my nightly builds can test other
> combinations of all other arch also.

Thanks.

It's commit 7fb5e5083190 ("mmu_gather: fix the
CONFIG_MMU_GATHER_NO_RANGE case") in my tree now.

I decided to not amend the commit, so it doesn't have your tested-by,
only your reported-by, but I put the link your report (this thread),
so it's kind of there.

                   Linus


      reply	other threads:[~2022-07-22 18:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-22  7:53 Sudip Mukherjee (Codethink)
2022-07-22 16:27 ` Linus Torvalds
2022-07-22 17:19   ` Sudip Mukherjee
2022-07-22 18:57     ` Linus Torvalds [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='CAHk-=whjFd-2j1qCsqdsakwcH=QML2BJBCpN2+rg10Y+PMGOOg@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=aneesh.kumar@linux.ibm.com \
    --cc=arnd@arndb.de \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=npiggin@gmail.com \
    --cc=peterz@infradead.org \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=will@kernel.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