From: Gabriele Monaco <gmonaco@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>, linux-kernel@vger.kernel.org
Cc: linux-trace-kernel@vger.kernel.org, Gabriele Monaco <gmonaco@redhat.com>
Subject: [GIT PULL] rv fixes for v7.3-rc1
Date: Tue, 25 Aug 2026 17:56:01 +0200 [thread overview]
Message-ID: <20260825155600.300355-2-gmonaco@redhat.com> (raw)
Steve,
The following changes since commit 7d81675d1bb2cc6db61a2d93b1e0dc7fb0929f9c:
Documentation/rv: Explain epoll and aborted sleeps (2026-08-04 16:11:28 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gmonaco/linux.git rv-fixes-7.3-rc1
for you to fetch changes up to ab0304fd69b07605553e9f161d65ecf9ccc2e2fe:
verification/rvgen: Use .old instead of .bak for kunit backup files (2026-08-25 13:56:53 +0200)
----------------------------------------------------------------
rv fixes for v7.3-rc1
Summary of changes:
- Use .old instead of .bak for rvgen kunit backup files
The rvgen kunit command generates .bak backup files and these are
checked in for selftests as "golden" files for make check. Clean
make disclean removes such files, leaving the tree dirty.
Switch to .old to preserve a clean tree after make disclean.
----------------------------------------------------------------
Gabriele Monaco (1):
verification/rvgen: Use .old instead of .bak for kunit backup files
tools/verification/rvgen/rvgen/kunit.py | 2 +-
.../{test_bak_kunit_kunit.c.bak => test_bak_kunit_kunit.c.old} | 0
2 files changed, 1 insertion(+), 1 deletion(-)
rename tools/verification/rvgen/tests/golden/test_bak_kunit/{test_bak_kunit_kunit.c.bak => test_bak_kunit_kunit.c.old} (100%)
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Gabriele Monaco <gmonaco@redhat.com>
reply other threads:[~2026-08-25 15:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260825155600.300355-2-gmonaco@redhat.com \
--to=gmonaco@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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.