From: patchwork-bot+linux-riscv@kernel.org
To: Jinjie Ruan <ruanjinjie@huawei.com>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu,
samitolvanen@google.com, debug@rivosinc.com,
andy.chiu@sifive.com, guoren@kernel.org,
songshuaishuai@tinylab.org, bjorn@rivosinc.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: Remove unused _TIF_WORK_MASK
Date: Tue, 17 Sep 2024 13:00:49 +0000 [thread overview]
Message-ID: <172657804950.126252.10342609864354079162.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240711111508.1373322-1-ruanjinjie@huawei.com>
Hello:
This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Thu, 11 Jul 2024 19:15:08 +0800 you wrote:
> Since commit f0bddf50586d ("riscv: entry: Convert to generic entry"),
> _TIF_WORK_MASK is no longer used, so remove it.
>
> Fixes: f0bddf50586d ("riscv: entry: Convert to generic entry")
> Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com>
> ---
> arch/riscv/include/asm/thread_info.h | 4 ----
> 1 file changed, 4 deletions(-)
Here is the summary with links:
- riscv: Remove unused _TIF_WORK_MASK
https://git.kernel.org/riscv/c/cea9d27705d6
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-09-17 13:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-11 11:15 [PATCH] riscv: Remove unused _TIF_WORK_MASK Jinjie Ruan
2024-07-14 8:40 ` Guo Ren
2024-08-20 2:41 ` Jinjie Ruan
2024-08-20 3:56 ` Andy Chiu
2024-09-17 13: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=172657804950.126252.10342609864354079162.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=andy.chiu@sifive.com \
--cc=aou@eecs.berkeley.edu \
--cc=bjorn@rivosinc.com \
--cc=debug@rivosinc.com \
--cc=guoren@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=ruanjinjie@huawei.com \
--cc=samitolvanen@google.com \
--cc=songshuaishuai@tinylab.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