All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Walmsley <pjw@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Paul Walmsley <pjw@kernel.org>, Nam Cao <namcao@linutronix.de>,
	 Rui Qi <qirui.001@bytedance.com>,
	linux-riscv@lists.infradead.org,
	 Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	 Alexandre Ghiti <alex@ghiti.fr>, Kees Cook <kees@kernel.org>,
	 Jingwei Wang <wangjingwei@iscas.ac.cn>,
	 open list <linux-kernel@vger.kernel.org>,
	 Linux-Next <linux-next@vger.kernel.org>
Subject: Re: [PATCH] riscv: hwprobe: Register unaligned probes before usermode
Date: Fri, 14 Aug 2026 11:04:00 -0600 (MDT)	[thread overview]
Message-ID: <1d36c93a-200e-3105-8ea2-36f20c382644@kernel.org> (raw)
In-Reply-To: <CAMuHMdUu16GZ0WX3tfpzThfmP21kW-u4JTg8NBQ1HKUDvfXORQ@mail.gmail.com>

Hi Geert,

On Fri, 14 Aug 2026, Geert Uytterhoeven wrote:

> On Tue, 11 Aug 2026 at 10:45, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> > On Sat, 8 Aug 2026 at 01:30, Paul Walmsley <pjw@kernel.org> wrote:
> > > On Fri, 7 Aug 2026, Nam Cao wrote:
> > > > Paul Walmsley <pjw@kernel.org> writes:
> > > > > Now that we've queued a patch to get rid of the async hwprobe
> > > > > infrastructure, is this patch still needed?
> > > >
> > > > Yes. Removing async probe only ensures probe is finished before the
> > > > kernel is done booting.
> > > >
> > > > But there are usermode helpers which run while the kernel is still booting.
> > > > This patch ensures probe is done before that.
> > >
> > > Okay, thanks for taking a look.
> > >
> > > Thanks Rui Qi for the patch; queued for v7.2-rc with a cc: to stable.
> >
> > This commit is now commit 994dad686e755477 in riscv/fixes.
> > However, riscv/for-next contains the similar but empty commit
> > acf3fcb5e9199cc9.  Presumably this is the result of a bad rebasing of
> > for-next on top of fixes?
> 
> The empty commit was rebased, and is now commit 4e864f1c3d8d147b.
> Please drop it (it breaks my scripting ;-).

Fixed!  Sorry about that,


- Paul

WARNING: multiple messages have this Message-ID (diff)
From: Paul Walmsley <pjw@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Paul Walmsley <pjw@kernel.org>, Nam Cao <namcao@linutronix.de>,
	 Rui Qi <qirui.001@bytedance.com>,
	linux-riscv@lists.infradead.org,
	 Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	 Alexandre Ghiti <alex@ghiti.fr>, Kees Cook <kees@kernel.org>,
	 Jingwei Wang <wangjingwei@iscas.ac.cn>,
	 open list <linux-kernel@vger.kernel.org>,
	 Linux-Next <linux-next@vger.kernel.org>
Subject: Re: [PATCH] riscv: hwprobe: Register unaligned probes before usermode
Date: Fri, 14 Aug 2026 11:04:00 -0600 (MDT)	[thread overview]
Message-ID: <1d36c93a-200e-3105-8ea2-36f20c382644@kernel.org> (raw)
In-Reply-To: <CAMuHMdUu16GZ0WX3tfpzThfmP21kW-u4JTg8NBQ1HKUDvfXORQ@mail.gmail.com>

Hi Geert,

On Fri, 14 Aug 2026, Geert Uytterhoeven wrote:

> On Tue, 11 Aug 2026 at 10:45, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> > On Sat, 8 Aug 2026 at 01:30, Paul Walmsley <pjw@kernel.org> wrote:
> > > On Fri, 7 Aug 2026, Nam Cao wrote:
> > > > Paul Walmsley <pjw@kernel.org> writes:
> > > > > Now that we've queued a patch to get rid of the async hwprobe
> > > > > infrastructure, is this patch still needed?
> > > >
> > > > Yes. Removing async probe only ensures probe is finished before the
> > > > kernel is done booting.
> > > >
> > > > But there are usermode helpers which run while the kernel is still booting.
> > > > This patch ensures probe is done before that.
> > >
> > > Okay, thanks for taking a look.
> > >
> > > Thanks Rui Qi for the patch; queued for v7.2-rc with a cc: to stable.
> >
> > This commit is now commit 994dad686e755477 in riscv/fixes.
> > However, riscv/for-next contains the similar but empty commit
> > acf3fcb5e9199cc9.  Presumably this is the result of a bad rebasing of
> > for-next on top of fixes?
> 
> The empty commit was rebased, and is now commit 4e864f1c3d8d147b.
> Please drop it (it breaks my scripting ;-).

Fixed!  Sorry about that,


- Paul

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

  reply	other threads:[~2026-08-14 17:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-21 15:05 [PATCH] riscv: hwprobe: Register unaligned probes before usermode Rui Qi
2026-07-21 15:05 ` Rui Qi
2026-07-22  7:52 ` Nam Cao
2026-07-22  7:52   ` Nam Cao
2026-07-28  3:57 ` Rui Qi
2026-07-28  3:57   ` Rui Qi
2026-08-06 18:50 ` Paul Walmsley
2026-08-06 18:50   ` Paul Walmsley
2026-08-07  6:07   ` Nam Cao
2026-08-07  6:07     ` Nam Cao
2026-08-07 23:29     ` Paul Walmsley
2026-08-07 23:29       ` Paul Walmsley
2026-08-11  8:45       ` Geert Uytterhoeven
2026-08-11  8:45         ` Geert Uytterhoeven
2026-08-14  9:19         ` Geert Uytterhoeven
2026-08-14  9:19           ` Geert Uytterhoeven
2026-08-14 17:04           ` Paul Walmsley [this message]
2026-08-14 17:04             ` Paul Walmsley

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=1d36c93a-200e-3105-8ea2-36f20c382644@kernel.org \
    --to=pjw@kernel.org \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=geert@linux-m68k.org \
    --cc=kees@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=namcao@linutronix.de \
    --cc=palmer@dabbelt.com \
    --cc=qirui.001@bytedance.com \
    --cc=wangjingwei@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.