From: Steven Rostedt <rostedt@goodmis.org>
To: Gabriele Monaco <gmonaco@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
unknownbbqrx <dev@unknownbbqr.xyz>, Wen Yang <wen.yang@linux.dev>
Subject: Re: [GIT PULL] rv fixes for v7.1
Date: Wed, 3 Jun 2026 19:16:27 -0400 [thread overview]
Message-ID: <20260603191627.5cb4ef6c@fedora> (raw)
In-Reply-To: <20260603125056.75559-1-gmonaco@redhat.com>
On Wed, 3 Jun 2026 14:50:56 +0200
Gabriele Monaco <gmonaco@redhat.com> wrote:
> unknownbbqrx (1):
> tools/rv: Ensure monitor name and desc are NUL-terminated
Hi Gabriele,
What is this? All commits need to be authored by and signed off by from
a real person with their official name.
https://docs.kernel.org/process/submitting-patches.html#sign-your-work-the-developer-s-certificate-of-origin
-- Steve
prev parent reply other threads:[~2026-06-03 23:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 12:50 [GIT PULL] rv fixes for v7.1 Gabriele Monaco
2026-06-03 23:16 ` Steven Rostedt [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=20260603191627.5cb4ef6c@fedora \
--to=rostedt@goodmis.org \
--cc=dev@unknownbbqr.xyz \
--cc=gmonaco@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=wen.yang@linux.dev \
/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