From: Nam Cao <namcao@linutronix.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: John Ogness <john.ogness@linutronix.de>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Gabriele Monaco <gmonaco@redhat.com>,
linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org,
Petr Mladek <pmladek@suse.com>,
Sergey Senozhatsky <senozhatsky@chromium.org>
Subject: Re: [PATCH v12 02/12] printk: Make vprintk_deferred() public
Date: Wed, 9 Jul 2025 21:09:38 +0200 [thread overview]
Message-ID: <20250709190938.8KErh6st@linutronix.de> (raw)
In-Reply-To: <20250709150452.6646c168@batman.local.home>
On Wed, Jul 09, 2025 at 03:04:52PM -0400, Steven Rostedt wrote:
> I could do it, but if you send a new version, it will keep patchwork
> automated. When I edit a patch, the status doesn't automatically get
> updated due to the change.
>
> I know it's minor, but could you send a v13? Then when the patch gets
> accepted in mainline, it should automatically turn to Accept in
> patchwork.
Fine for me either way. I worked with other maintainers who prefer the
other way, so I had to ask.
Nam
next prev parent reply other threads:[~2025-07-09 19:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 17:56 [PATCH v12 00/12] RV: Linear temporal logic monitors for RT application Nam Cao
2025-07-09 17:56 ` [PATCH v12 01/12] rv: Add #undef TRACE_INCLUDE_FILE Nam Cao
2025-07-09 17:56 ` [PATCH v12 02/12] printk: Make vprintk_deferred() public Nam Cao
2025-07-09 18:49 ` Steven Rostedt
2025-07-09 18:53 ` Nam Cao
2025-07-09 19:04 ` Steven Rostedt
2025-07-09 19:09 ` Nam Cao [this message]
2025-07-09 19:21 ` Steven Rostedt
2025-07-09 17:56 ` [PATCH v12 03/12] panic: Add vpanic() Nam Cao
2025-07-09 17:56 ` [PATCH v12 04/12] rv: Let the reactors take care of buffers Nam Cao
2025-07-09 17:56 ` [PATCH v12 05/12] rv: rename CONFIG_DA_MON_EVENTS to CONFIG_RV_MON_EVENTS Nam Cao
2025-07-09 17:56 ` [PATCH v12 06/12] rv: Add support for LTL monitors Nam Cao
2025-07-09 17:56 ` [PATCH v12 07/12] rv: Add rtapp container monitor Nam Cao
2025-07-09 17:56 ` [PATCH v12 08/12] riscv: mm: Add page fault trace points Nam Cao
2025-07-09 17:56 ` [PATCH v12 09/12] rv: Add rtapp_pagefault monitor Nam Cao
2025-07-09 17:56 ` [PATCH v12 10/12] rv: Add rtapp_sleep monitor Nam Cao
2025-07-09 17:56 ` [PATCH v12 11/12] rv: Add documentation for rtapp monitor Nam Cao
2025-07-09 17:56 ` [PATCH v12 12/12] rv: Allow to configure the number of per-task monitor Nam Cao
2025-07-09 18:02 ` [PATCH v12 00/12] RV: Linear temporal logic monitors for RT application Steven Rostedt
2025-07-09 18:36 ` Nam Cao
2025-08-10 21:12 ` 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=20250709190938.8KErh6st@linutronix.de \
--to=namcao@linutronix.de \
--cc=gmonaco@redhat.com \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®