From: patchwork-bot+linux-riscv@kernel.org
To: Palmer Dabbelt <palmer@rivosinc.com>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu, surenb@google.com,
akpm@linux-foundation.org, alexghiti@rivosinc.com,
wangkefeng.wang@huawei.com, jszhang@kernel.org,
ben@decadent.org.uk, bjorn@rivosinc.com, willy@infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Revert "riscv: mm: accelerate pagefault when badaccess"
Date: Fri, 31 May 2024 16:00:36 +0000 [thread overview]
Message-ID: <171717123679.27814.3225238698035039427.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240530164451.21336-1-palmer@rivosinc.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Thu, 30 May 2024 09:44:51 -0700 you wrote:
> From: Palmer Dabbelt <palmer@rivosinc.com>
>
> I accidentally picked up an earlier version of this patch, which had
> already landed via mm. The patch I picked up contains a bug, which I
> kept as I thought it was a fix. So let's just revert it.
>
> This reverts commit 4c6c0020427a4547845a83f7e4d6085e16c3e24f.
>
> [...]
Here is the summary with links:
- Revert "riscv: mm: accelerate pagefault when badaccess"
https://git.kernel.org/riscv/c/7932b172ac7e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2024-05-31 16:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 16:44 [PATCH] Revert "riscv: mm: accelerate pagefault when badaccess" Palmer Dabbelt
2024-05-31 4:05 ` Kefeng Wang
2024-05-31 5:45 ` Alexandre Ghiti
2024-05-31 16:00 ` patchwork-bot+linux-riscv [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=171717123679.27814.3225238698035039427.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alexghiti@rivosinc.com \
--cc=aou@eecs.berkeley.edu \
--cc=ben@decadent.org.uk \
--cc=bjorn@rivosinc.com \
--cc=jszhang@kernel.org \
--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=surenb@google.com \
--cc=wangkefeng.wang@huawei.com \
--cc=willy@infradead.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