public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nam Cao <namcao@linutronix.de>
To: Thomas Huth <thuth@redhat.com>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Paul Walmsley <pjw@kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Alexandre Ghiti <alex@ghiti.fr>,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] riscv: Add kprobes KUnit test
Date: Mon, 29 Sep 2025 12:19:27 +0200	[thread overview]
Message-ID: <87v7l17e8g.fsf@yellow.woof> (raw)
In-Reply-To: <87frc9h0lo.fsf@yellow.woof>

Nam Cao <namcao@linutronix.de> writes:
> Thomas Huth <thuth@redhat.com> writes:
>> Could you maybe change that into "__ASSEMBLER__" instead of "__ASSEMBLY__" ? 
>> I'm currently trying to get rid of the latter in the kernel sources, see: 
>> https://lore.kernel.org/all/20250606070952.498274-1-thuth@redhat.com/
>
> It's been applied, it's up to riscv's maintainers how we should do this.
>
> I can send v3, or a follow-up patch.
>
> Or riscv maintainers can also squash that change into this patch, or
> into your patch.
>
> I'm fine with any options.

Riscv pull request is already created. A follow-up patch it is then.

Nam

  reply	other threads:[~2025-09-29 10:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-13 15:16 [PATCH v2] riscv: Add kprobes KUnit test Nam Cao
2025-05-14  8:22 ` Alexandre Ghiti
2025-05-14 10:01   ` Nam Cao
2025-06-04 14:33 ` patchwork-bot+linux-riscv
2025-09-26 11:51 ` Thomas Huth
2025-09-26 12:14   ` Nam Cao
2025-09-29 10:19     ` Nam Cao [this message]
2025-10-10 22:03       ` Paul Walmsley
2025-10-13  5:15         ` Thomas Huth

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=87v7l17e8g.fsf@yellow.woof \
    --to=namcao@linutronix.de \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=pjw@kernel.org \
    --cc=thuth@redhat.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