From: Will Deacon <will@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: mm-commits@vger.kernel.org, wangkefeng.wang@huawei.com,
robin.murphy@arm.com, quic_pkondeti@quicinc.com,
mark.rutland@arm.com, jianyong.wu@arm.com, james.morse@arm.com,
glider@google.com, elver@google.com, dvyukov@google.com,
catalin.marinas@arm.com, quic_zhenhuah@quicinc.com
Subject: Re: + mmkfence-decouple-kfence-from-page-granularity-mapping-judgement.patch added to mm-unstable branch
Date: Fri, 24 Mar 2023 17:30:41 +0000 [thread overview]
Message-ID: <20230324173040.GA27948@willie-the-truck> (raw)
In-Reply-To: <20230317190042.32FC0C4339C@smtp.kernel.org>
Hi Andrew,
On Fri, Mar 17, 2023 at 12:00:41PM -0700, Andrew Morton wrote:
>
> The patch titled
> Subject: mm,kfence: decouple kfence from page granularity mapping judgement
> has been added to the -mm mm-unstable branch. Its filename is
> mmkfence-decouple-kfence-from-page-granularity-mapping-judgement.patch
>
> This patch will shortly appear at
> https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/mmkfence-decouple-kfence-from-page-granularity-mapping-judgement.patch
Do you mind if I pick this one up via -arm64? It's pretty much all arch
changes, and I'd like to avoid any cross-tree conflicts in the mm/ code
if possible.
Cheers,
Will
next prev parent reply other threads:[~2023-03-24 17:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 19:00 + mmkfence-decouple-kfence-from-page-granularity-mapping-judgement.patch added to mm-unstable branch Andrew Morton
2023-03-24 17:30 ` Will Deacon [this message]
2023-03-24 18:52 ` Andrew Morton
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=20230324173040.GA27948@willie-the-truck \
--to=will@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=james.morse@arm.com \
--cc=jianyong.wu@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mm-commits@vger.kernel.org \
--cc=quic_pkondeti@quicinc.com \
--cc=quic_zhenhuah@quicinc.com \
--cc=robin.murphy@arm.com \
--cc=wangkefeng.wang@huawei.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).