From: Greg KH <gregkh@linuxfoundation.org>
To: Vivian Wang <wangruikang@iscas.ac.cn>
Cc: stable@vger.kernel.org, Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Paul Walmsley <paul.walmsley@sifive.com>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
Guo Ren <guoren@kernel.org>,
Charlie Jenkins <charlie@rivosinc.com>,
Yangyu Chen <cyy@cyyself.name>, Han Gao <rabenda.cn@gmail.com>,
Icenowy Zheng <uwu@icenowy.me>,
Inochi Amaoto <inochiama@gmail.com>, Yao Zi <ziyao@disroot.org>,
Palmer Dabbelt <palmer@rivosinc.com>
Subject: Re: [PATCH 6.6.y 0/2] riscv: mm: Backport of mmap hint address fixes
Date: Wed, 8 Oct 2025 12:20:26 +0200 [thread overview]
Message-ID: <2025100812-raven-goes-4fd8@gregkh> (raw)
In-Reply-To: <20251008-riscv-mmap-addr-space-6-6-v1-0-9f47574a520f@iscas.ac.cn>
On Wed, Oct 08, 2025 at 03:50:15PM +0800, Vivian Wang wrote:
> Backport of the two riscv mmap patches from master. In effect, these two
> patches removes arch_get_mmap_{base,end} for riscv.
Why is this needed? What bug does this fix?
thanks,
greg k-h
next prev parent reply other threads:[~2025-10-08 10:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-08 7:50 [PATCH 6.6.y 0/2] riscv: mm: Backport of mmap hint address fixes Vivian Wang
2025-10-08 7:50 ` [PATCH 6.6.y 1/2] riscv: mm: Use hint address in mmap if available Vivian Wang
2025-10-08 7:50 ` [PATCH 6.6.y 2/2] riscv: mm: Do not restrict mmap address based on hint Vivian Wang
2025-10-08 10:20 ` Greg KH [this message]
2025-10-09 4:19 ` [PATCH 6.6.y 0/2] riscv: mm: Backport of mmap hint address fixes Vivian Wang
2025-10-09 5:00 ` Greg KH
2025-10-09 5:50 ` Vivian Wang
2025-10-09 13:31 ` Greg KH
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=2025100812-raven-goes-4fd8@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=aou@eecs.berkeley.edu \
--cc=charlie@rivosinc.com \
--cc=cyy@cyyself.name \
--cc=guoren@kernel.org \
--cc=inochiama@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=palmer@rivosinc.com \
--cc=paul.walmsley@sifive.com \
--cc=pjw@kernel.org \
--cc=rabenda.cn@gmail.com \
--cc=stable@vger.kernel.org \
--cc=uwu@icenowy.me \
--cc=wangruikang@iscas.ac.cn \
--cc=ziyao@disroot.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