Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Miquel Sabaté Solà" <mikisabate@gmail.com>
To: Alexandre Ghiti <alex@ghiti.fr>
Cc: paul.walmsley@sifive.com,  palmer@dabbelt.com,
	linux-riscv@lists.infradead.org,  linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Improve Kconfig help for RISCV_ISA_V_PREEMPTIVE
Date: Tue, 06 May 2025 10:39:02 +0200	[thread overview]
Message-ID: <6819caa8.a70a0220.771e1.2b4b@mx.google.com> (raw)
In-Reply-To: <ceccc081-2dd5-4828-8eaf-148b48e05eda@ghiti.fr> (Alexandre Ghiti's message of "Tue, 6 May 2025 10:33:24 +0200")


[-- Attachment #1.1: Type: text/plain, Size: 1786 bytes --]

On dt., de maig 06 2025, Alexandre Ghiti wrote:

> Hi Miquel,
>
> Your patch title should be prefixed with "riscv" or "RISC-V", but no need to
> resend, I'll fix it when I merge your patch.

Yikes! I'll keep this in mind next time. Thanks!

>
> On 01/05/2025 15:03, mikisabate@gmail.com wrote:
>> From: Miquel Sabaté Solà <mikisabate@gmail.com>
>>
>> Fix a couple of spelling issues plus some minor details on the grammar.
>>
>> Signed-off-by: Miquel Sabaté Solà <mikisabate@gmail.com>
>> ---
>>   arch/riscv/Kconfig | 8 ++++----
>>   1 file changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig
>> index 1fd197afd2f7..3f40e33bc115 100644
>> --- a/arch/riscv/Kconfig
>> +++ b/arch/riscv/Kconfig
>> @@ -664,12 +664,12 @@ config RISCV_ISA_V_PREEMPTIVE
>>   	default y
>>   	help
>>   	  Usually, in-kernel SIMD routines are run with preemption disabled.
>> -	  Functions which envoke long running SIMD thus must yield core's
>> +	  Functions which invoke long running SIMD thus must yield the core's
>>   	  vector unit to prevent blocking other tasks for too long.
>>   -	  This config allows kernel to run SIMD without explicitly disable
>> -	  preemption. Enabling this config will result in higher memory
>> -	  consumption due to the allocation of per-task's kernel Vector context.
>> +	  This config allows the kernel to run SIMD without explicitly disabling
>> +	  preemption. Enabling this config will result in higher memory consumption
>> +	  due to the allocation of per-task's kernel Vector context.
>>     config RISCV_ISA_ZAWRS
>>   	bool "Zawrs extension support for more efficient busy waiting"
>
>
> Reviewed-by: Alexandre Ghiti <alexghiti@rivosinc.com>
>
> Thanks,
>
> Alex

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]

[-- Attachment #2: Type: text/plain, Size: 161 bytes --]

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2025-05-06  9:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-01 13:03 [PATCH] Improve Kconfig help for RISCV_ISA_V_PREEMPTIVE mikisabate
2025-05-06  8:33 ` Alexandre Ghiti
2025-05-06  8:39   ` Miquel Sabaté Solà [this message]
2025-06-02 22:12 ` patchwork-bot+linux-riscv

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=6819caa8.a70a0220.771e1.2b4b@mx.google.com \
    --to=mikisabate@gmail.com \
    --cc=alex@ghiti.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@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