From: Nam Cao <namcao@linutronix.de>
To: Gabriele Monaco <gmonaco@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org,
John Ogness <john.ogness@linutronix.de>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] rv/rtapp/wakeup: Use "rv_this" the rv_monitor variable
Date: Fri, 02 Oct 2026 17:33:48 +0200 [thread overview]
Message-ID: <874if415ib.fsf@yellow.woof> (raw)
In-Reply-To: <e91ee6fcd36a6ae4616fbd61121b2354594099f9.camel@redhat.com>
Gabriele Monaco <gmonaco@redhat.com> writes:
> d9e4c61a12dd was introduced in the same pull request but after introducing the
> wakeup monitor.
> So for me that's the commit that is "broken" (should have accounted for wakeup):
>
> Fixes: d9e4c61a12dd ("rv: Use generic rv_this for the rv_monitor variable in
> LTL")
Sorry, I was lost in the sick land, and now see you already opened the PR.
But yes, I agree that the commit applied later should be in Fixes:.
Nam
prev parent reply other threads:[~2026-10-02 15:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 4:42 [PATCH] rv/rtapp/wakeup: Use "rv_this" the rv_monitor variable Nam Cao
2026-10-01 6:31 ` Gabriele Monaco
2026-10-01 11:17 ` Gabriele Monaco
2026-10-02 15:33 ` Nam Cao [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=874if415ib.fsf@yellow.woof \
--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=rostedt@goodmis.org \
--cc=stable@vger.kernel.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.