From: Pavel Tatashin <pasha.tatashin@soleen.com>
To: Will Deacon <will@kernel.org>
Cc: Tyler Hicks <tyhicks@linux.microsoft.com>,
James Morris <jmorris@namei.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Mike Rapoport <rppt@kernel.org>,
Logan Gunthorpe <logang@deltatee.com>,
Ard Biesheuvel <ardb@kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Michal Hocko <mhocko@suse.com>, linux-mm <linux-mm@kvack.org>
Subject: Re: [PATCH v3 1/1] arm64: mm: correct the inside linear map range during hotplug check
Date: Mon, 22 Feb 2021 09:17:18 -0500 [thread overview]
Message-ID: <CA+CK2bB73ezoajLaK63+WWKjDxOBiPNPv9Akj8mtJuvBvhLOZQ@mail.gmail.com> (raw)
In-Reply-To: <20210222122545.GA8847@willie-the-truck>
> Taking that won't help either though, because it will just explode when
> it meets 'mm' in Linus's tree.
>
> So here's what I think we need to do:
>
> - I'll apply your v3 at -rc1
> - You can send backports based on your -v2 for stable once the v3 has
> been merged upstream.
>
> Sound good?
Sounds good, I will send backport once v3 lands in Linus's tree.
Thanks,
Pasha
>
> Will
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Tatashin <pasha.tatashin@soleen.com>
To: Will Deacon <will@kernel.org>
Cc: Michal Hocko <mhocko@suse.com>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
James Morris <jmorris@namei.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Tyler Hicks <tyhicks@linux.microsoft.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Logan Gunthorpe <logang@deltatee.com>,
Ard Biesheuvel <ardb@kernel.org>, Mike Rapoport <rppt@kernel.org>
Subject: Re: [PATCH v3 1/1] arm64: mm: correct the inside linear map range during hotplug check
Date: Mon, 22 Feb 2021 09:17:18 -0500 [thread overview]
Message-ID: <CA+CK2bB73ezoajLaK63+WWKjDxOBiPNPv9Akj8mtJuvBvhLOZQ@mail.gmail.com> (raw)
In-Reply-To: <20210222122545.GA8847@willie-the-truck>
> Taking that won't help either though, because it will just explode when
> it meets 'mm' in Linus's tree.
>
> So here's what I think we need to do:
>
> - I'll apply your v3 at -rc1
> - You can send backports based on your -v2 for stable once the v3 has
> been merged upstream.
>
> Sound good?
Sounds good, I will send backport once v3 lands in Linus's tree.
Thanks,
Pasha
>
> Will
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-02-22 14:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-16 15:03 [PATCH v3 0/1] correct the inside linear map range during hotplug check Pavel Tatashin
2021-02-16 15:03 ` Pavel Tatashin
2021-02-16 15:03 ` [PATCH v3 1/1] arm64: mm: " Pavel Tatashin
2021-02-16 15:03 ` Pavel Tatashin
2021-02-19 19:18 ` Will Deacon
2021-02-19 19:18 ` Will Deacon
2021-02-19 19:44 ` Pavel Tatashin
2021-02-19 19:44 ` Pavel Tatashin
2021-02-19 19:44 ` Pavel Tatashin
2021-02-22 12:25 ` Will Deacon
2021-02-22 12:25 ` Will Deacon
2021-02-22 14:17 ` Pavel Tatashin [this message]
2021-02-22 14:17 ` Pavel Tatashin
2021-02-22 14:17 ` Pavel Tatashin
2021-03-19 15:43 ` Pavel Tatashin
2021-03-19 15:43 ` Pavel Tatashin
2021-03-19 15:43 ` Pavel Tatashin
2021-02-24 7:12 ` Anshuman Khandual
2021-02-24 7:12 ` Anshuman Khandual
2021-03-22 13:19 ` [PATCH v3 0/1] " Will Deacon
2021-03-22 13:19 ` Will Deacon
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=CA+CK2bB73ezoajLaK63+WWKjDxOBiPNPv9Akj8mtJuvBvhLOZQ@mail.gmail.com \
--to=pasha.tatashin@soleen.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=jmorris@namei.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=logang@deltatee.com \
--cc=mhocko@suse.com \
--cc=rppt@kernel.org \
--cc=tyhicks@linux.microsoft.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 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.