All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Walmsley <pjw@kernel.org>
To: Chunyan Zhang <zhang.lyra@gmail.com>
Cc: Alexandre Ghiti <alex@ghiti.fr>,
	Chunyan Zhang <zhangchunyan@iscas.ac.cn>,
	 Paul Walmsley <paul.walmsley@sifive.com>,
	 Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	 Charlie Jenkins <charlie@rivosinc.com>,
	Song Liu <song@kernel.org>,  Yu Kuai <yukuai3@huawei.com>,
	linux-riscv@lists.infradead.org,  linux-raid@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3 5/5] raid6: test: Add support for RISC-V
Date: Tue, 25 Nov 2025 02:29:53 -0700 (MST)	[thread overview]
Message-ID: <2b81141c-2fcf-3083-e99f-a6205e121ab3@kernel.org> (raw)
In-Reply-To: <CAAfSe-umv64D011cjxPJEc0dBK29Xa4u6m1T=-THZ+V=a3f+JA@mail.gmail.com>

Hi Chunyan Zhang,

On Mon, 13 Oct 2025, Chunyan Zhang wrote:

> I noticed patch 1-2 are in 6.18-rc1, patch 3-5 haven't got merged, not
> sure if there's some other plan for these patches.

Those were deferred since I wanted more time to review them.  I've queued 
them for v6.19.

thanks,

- Paul

WARNING: multiple messages have this Message-ID (diff)
From: Paul Walmsley <pjw@kernel.org>
To: Chunyan Zhang <zhang.lyra@gmail.com>
Cc: Alexandre Ghiti <alex@ghiti.fr>,
	Chunyan Zhang <zhangchunyan@iscas.ac.cn>,
	 Paul Walmsley <paul.walmsley@sifive.com>,
	 Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	 Charlie Jenkins <charlie@rivosinc.com>,
	Song Liu <song@kernel.org>,  Yu Kuai <yukuai3@huawei.com>,
	linux-riscv@lists.infradead.org,  linux-raid@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3 5/5] raid6: test: Add support for RISC-V
Date: Tue, 25 Nov 2025 02:29:53 -0700 (MST)	[thread overview]
Message-ID: <2b81141c-2fcf-3083-e99f-a6205e121ab3@kernel.org> (raw)
In-Reply-To: <CAAfSe-umv64D011cjxPJEc0dBK29Xa4u6m1T=-THZ+V=a3f+JA@mail.gmail.com>

Hi Chunyan Zhang,

On Mon, 13 Oct 2025, Chunyan Zhang wrote:

> I noticed patch 1-2 are in 6.18-rc1, patch 3-5 haven't got merged, not
> sure if there's some other plan for these patches.

Those were deferred since I wanted more time to review them.  I've queued 
them for v6.19.

thanks,

- Paul

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

  reply	other threads:[~2025-11-25  9:29 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-18  7:27 [PATCH V3 0/5] Add an optimization also raid6test for RISC-V support Chunyan Zhang
2025-07-18  7:27 ` Chunyan Zhang
2025-07-18  7:27 ` [PATCH V3 1/5] raid6: riscv: Clean up unused header file inclusion Chunyan Zhang
2025-07-18  7:27   ` Chunyan Zhang
2025-07-18  7:27 ` [PATCH V3 2/5] raid6: riscv: replace one load with a move to speed up the caculation Chunyan Zhang
2025-07-18  7:27   ` Chunyan Zhang
2025-07-18  7:27 ` [PATCH V3 3/5] raid6: riscv: Prevent compiler with vector support to build already vectorized code Chunyan Zhang
2025-07-18  7:27   ` Chunyan Zhang
2025-11-25  9:26   ` Paul Walmsley
2025-11-25  9:26     ` Paul Walmsley
2025-11-25  9:43     ` Chunyan Zhang
2025-11-25  9:43       ` Chunyan Zhang
2025-07-18  7:27 ` [PATCH V3 4/5] raid6: riscv: Allow code to be compiled in userspace Chunyan Zhang
2025-07-18  7:27   ` Chunyan Zhang
2025-07-18  7:27 ` [PATCH V3 5/5] raid6: test: Add support for RISC-V Chunyan Zhang
2025-07-18  7:27   ` Chunyan Zhang
2025-07-18 14:08   ` Alexandre Ghiti
2025-07-18 14:08     ` Alexandre Ghiti
2025-10-13  1:42     ` Chunyan Zhang
2025-10-13  1:42       ` Chunyan Zhang
2025-11-25  9:29       ` Paul Walmsley [this message]
2025-11-25  9:29         ` Paul Walmsley
2025-08-06 17:15 ` [PATCH V3 0/5] Add an optimization also raid6test for RISC-V support patchwork-bot+linux-riscv
2025-08-06 17:15   ` 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=2b81141c-2fcf-3083-e99f-a6205e121ab3@kernel.org \
    --to=pjw@kernel.org \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=charlie@rivosinc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=song@kernel.org \
    --cc=yukuai3@huawei.com \
    --cc=zhang.lyra@gmail.com \
    --cc=zhangchunyan@iscas.ac.cn \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.