Linux-RISC-V Archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Charlie Jenkins <charlie@rivosinc.com>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
	palmer@dabbelt.com, aou@eecs.berkeley.edu, corbet@lwn.net,
	conor.dooley@microchip.com, cleger@rivosinc.com,
	atishp@atishpatra.org, rdunlap@infradead.org, alex@ghiti.fr,
	samuel.holland@sifive.com, linux-kernel@vger.kernel.org,
	linux-doc@vger.kernel.org, atishp@rivosinc.com,
	alexghiti@rivosinc.com
Subject: Re: [PATCH v13 0/4] riscv: Create and document PR_RISCV_SET_ICACHE_FLUSH_CTX prctl
Date: Sun, 28 Apr 2024 22:00:34 +0000	[thread overview]
Message-ID: <171434163491.22130.7402887915365003575.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240312-fencei-v13-0-4b6bdc2bbf32@rivosinc.com>

Hello:

This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:

On Tue, 12 Mar 2024 16:53:39 -0700 you wrote:
> Improve the performance of icache flushing by creating a new prctl flag
> PR_RISCV_SET_ICACHE_FLUSH_CTX. The interface is left generic to allow
> for future expansions such as with the proposed J extension [1].
> 
> Documentation is also provided to explain the use case.
> 
> Patch sent to add PR_RISCV_SET_ICACHE_FLUSH_CTX to man-pages [2].
> 
> [...]

Here is the summary with links:
  - [v13,1/4] riscv: Remove unnecessary irqflags processor.h include
    https://git.kernel.org/riscv/c/bebc345413f5
  - [v13,2/4] riscv: Include riscv_set_icache_flush_ctx prctl
    https://git.kernel.org/riscv/c/6b9391b581fd
  - [v13,3/4] documentation: Document PR_RISCV_SET_ICACHE_FLUSH_CTX prctl
    https://git.kernel.org/riscv/c/6a08e4709c58
  - [v13,4/4] cpumask: Add assign cpu
    https://git.kernel.org/riscv/c/decde1fa2093

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

      parent reply	other threads:[~2024-04-28 22:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-12 23:53 [PATCH v13 0/4] riscv: Create and document PR_RISCV_SET_ICACHE_FLUSH_CTX prctl Charlie Jenkins
2024-03-12 23:53 ` [PATCH v13 1/4] riscv: Remove unnecessary irqflags processor.h include Charlie Jenkins
2024-03-12 23:53 ` [PATCH v13 2/4] riscv: Include riscv_set_icache_flush_ctx prctl Charlie Jenkins
2024-03-12 23:56   ` Samuel Holland
2024-03-12 23:53 ` [PATCH v13 3/4] documentation: Document PR_RISCV_SET_ICACHE_FLUSH_CTX prctl Charlie Jenkins
2024-03-12 23:53 ` [PATCH v13 4/4] cpumask: Add assign cpu Charlie Jenkins
2024-04-28 22: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=171434163491.22130.7402887915365003575.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=alex@ghiti.fr \
    --cc=alexghiti@rivosinc.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=atishp@atishpatra.org \
    --cc=atishp@rivosinc.com \
    --cc=charlie@rivosinc.com \
    --cc=cleger@rivosinc.com \
    --cc=conor.dooley@microchip.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=rdunlap@infradead.org \
    --cc=samuel.holland@sifive.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 read-only IMAP folder(s) and NNTP newsgroup(s).