All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Walmsley <pjw@kernel.org>
To: Vivian Wang <wangruikang@iscas.ac.cn>
Cc: Paul Sherman <shermanpauldylan@gmail.com>,
	Paul Walmsley <pjw@kernel.org>,
	 linux-riscv@lists.infradead.org, palmer@dabbelt.com,
	 paul.walmsley@sifive.com, aou@eecs.berkeley.edu
Subject: Re: [PATCH v2] riscv: smp: set CPU 0 possible in setup_smp()
Date: Wed, 15 Jul 2026 08:14:40 -0600 (MDT)	[thread overview]
Message-ID: <8a2944c4-dad0-87cc-85be-15033639a7ae@kernel.org> (raw)
In-Reply-To: <512ccb67-3b5d-4ae9-b74a-56275443ad49@iscas.ac.cn>

On Wed, 15 Jul 2026, Vivian Wang wrote:

> Given that neither visual analysis (see above) nor runtime testing (we
> have SG2042 machines in ISCAS running 7.0.x and 7.1.x without running
> into this) can confirm that this bug exists, I'm concluding that, unless
> further convincing evidence otherwise comes up, this is a bug you
> introduced in your tree and does not fixing for mainline.

Thanks for taking a closer look, Vivian; I'll drop this patch for now 
until either Paul or someone else can reproduce this on mainline.


- Paul



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

      reply	other threads:[~2026-07-15 14:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-14 22:33 [PATCH v2] riscv: smp: set CPU 0 possible in setup_smp() Paul Sherman
2026-07-15  1:41 ` Paul Walmsley
2026-07-15  4:01   ` Vivian Wang
2026-07-15  4:51     ` Paul Sherman
2026-07-15  6:20       ` Vivian Wang
2026-07-15 14:14         ` Paul Walmsley [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=8a2944c4-dad0-87cc-85be-15033639a7ae@kernel.org \
    --to=pjw@kernel.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=shermanpauldylan@gmail.com \
    --cc=wangruikang@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.