All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yao Zi <ziyao@disroot.org>
To: Paul Walmsley <pjw@kernel.org>, torvalds@linux-foundation.org
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Han Gao <rabenda.cn@gmail.com>
Subject: Re: [GIT PULL] RISC-V updates for v6.18-rc1
Date: Sat, 11 Oct 2025 08:38:22 +0000	[thread overview]
Message-ID: <aOoXYHaFe-R7ZySY@pie> (raw)
In-Reply-To: <2c804359-3d43-0fba-7173-a87f9aec4bd2@kernel.org>

Hi Paul, Palmer,

On Mon, Sep 29, 2025 at 02:00:17AM -0600, Paul Walmsley wrote:
> Linus,
> 
> The following changes since commit a03ee11b8f850bd008226c6d392da24163dfb56e:
> 
>   riscv: Fix sparse warning about different address spaces (2025-09-05 15:33:52 -0600)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux tags/riscv-for-linus-6.18-mw1
> 
> for you to fetch changes up to 0b0ca959d20689fece038954bbf1d7b14c0b11c3:
> 
>   riscv: errata: Fix the PAUSE Opcode for MIPS P8700 (2025-09-19 10:33:56 -0600)

...

> Guo Ren (Alibaba DAMO Academy) (1):
>       riscv: Move vendor errata definitions to new header

As already noted by Han Gao[1], it seems the second patch of series
"riscv: errata: Add ERRATA_THEAD_WRITE_ONCE fixup"[2] is included in the
pull request for 6.17-rc1, but not this one for 6.18-rc1. Is this
expected?

Best regards,
Yao Zi

[1]: https://lore.kernel.org/all/CAAT7Ki9_Vm0+v9RHpa2w-Bg3agJy2Tp4d6+tcPJ=M7XX3GV-7Q@mail.gmail.com/
[2]: https://lore.kernel.org/all/20250713155321.2064856-1-guoren@kernel.org/

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

WARNING: multiple messages have this Message-ID (diff)
From: Yao Zi <ziyao@disroot.org>
To: Paul Walmsley <pjw@kernel.org>, torvalds@linux-foundation.org
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Han Gao <rabenda.cn@gmail.com>
Subject: Re: [GIT PULL] RISC-V updates for v6.18-rc1
Date: Sat, 11 Oct 2025 08:38:22 +0000	[thread overview]
Message-ID: <aOoXYHaFe-R7ZySY@pie> (raw)
In-Reply-To: <2c804359-3d43-0fba-7173-a87f9aec4bd2@kernel.org>

Hi Paul, Palmer,

On Mon, Sep 29, 2025 at 02:00:17AM -0600, Paul Walmsley wrote:
> Linus,
> 
> The following changes since commit a03ee11b8f850bd008226c6d392da24163dfb56e:
> 
>   riscv: Fix sparse warning about different address spaces (2025-09-05 15:33:52 -0600)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux tags/riscv-for-linus-6.18-mw1
> 
> for you to fetch changes up to 0b0ca959d20689fece038954bbf1d7b14c0b11c3:
> 
>   riscv: errata: Fix the PAUSE Opcode for MIPS P8700 (2025-09-19 10:33:56 -0600)

...

> Guo Ren (Alibaba DAMO Academy) (1):
>       riscv: Move vendor errata definitions to new header

As already noted by Han Gao[1], it seems the second patch of series
"riscv: errata: Add ERRATA_THEAD_WRITE_ONCE fixup"[2] is included in the
pull request for 6.17-rc1, but not this one for 6.18-rc1. Is this
expected?

Best regards,
Yao Zi

[1]: https://lore.kernel.org/all/CAAT7Ki9_Vm0+v9RHpa2w-Bg3agJy2Tp4d6+tcPJ=M7XX3GV-7Q@mail.gmail.com/
[2]: https://lore.kernel.org/all/20250713155321.2064856-1-guoren@kernel.org/

  parent reply	other threads:[~2025-10-11  8:39 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-29  8:00 [GIT PULL] RISC-V updates for v6.18-rc1 Paul Walmsley
2025-09-29  8:00 ` Paul Walmsley
2025-09-30  2:54 ` pr-tracker-bot
2025-09-30  2:54   ` pr-tracker-bot
2025-09-30  7:25 ` Ben Dooks
2025-09-30  7:25   ` Ben Dooks
2025-09-30 16:04   ` Linus Torvalds
2025-09-30 16:04     ` Linus Torvalds
2025-09-30 23:53     ` Linus Torvalds
2025-09-30 23:53       ` Linus Torvalds
2025-10-01 18:33       ` Eric Biggers
2025-10-01 18:33         ` Eric Biggers
2025-10-03  1:45         ` Yury Norov
2025-10-03  1:45           ` Yury Norov
2025-10-01 19:02       ` Conor Dooley
2025-10-01 19:02         ` Conor Dooley
2025-10-01 19:39         ` Linus Torvalds
2025-10-01 19:39           ` Linus Torvalds
2025-10-02 12:48     ` Ben Dooks
2025-10-02 12:48       ` Ben Dooks
2025-10-02 15:06       ` Olof Johansson
2025-10-02 15:06         ` Olof Johansson
2025-10-02 15:22         ` Ben Dooks
2025-10-02 15:22           ` Ben Dooks
2025-10-07 23:43         ` Maciej W. Rozycki
2025-10-07 23:43           ` Maciej W. Rozycki
2025-10-20 23:31           ` Paul Walmsley
2025-10-20 23:31             ` Paul Walmsley
2025-10-02 18:08       ` Theodore Ts'o
2025-10-02 18:08         ` Theodore Ts'o
2025-10-11  8:38 ` Yao Zi [this message]
2025-10-11  8:38   ` Yao Zi

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=aOoXYHaFe-R7ZySY@pie \
    --to=ziyao@disroot.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=pjw@kernel.org \
    --cc=rabenda.cn@gmail.com \
    --cc=torvalds@linux-foundation.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 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.