From: Steven Rostedt <rostedt@goodmis.org>
To: Alice Ryhl <aliceryhl@google.com>
Cc: lkp@intel.com, boqun.feng@gmail.com, llvm@lists.linux.dev,
oe-kbuild-all@lists.linux.dev, ojeda@kernel.org,
linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] jump_label: rust: pass a mut ptr to `static_key_count`
Date: Tue, 19 Nov 2024 10:53:47 -0500 [thread overview]
Message-ID: <20241119105347.32cbd654@gandalf.local.home> (raw)
In-Reply-To: <CAH5fLgiyWDiDFAJO-LDj_ZdRjSnqh-j7vw7URLUm8ZHiFKfGXw@mail.gmail.com>
On Tue, 19 Nov 2024 16:31:40 +0100
Alice Ryhl <aliceryhl@google.com> wrote:
> > Would you be able to create some simple code to do that? If you add
> > something in the rust sample code, I'll add it to the ftrace selftests.
>
> Sure, I'll submit a sample which does that for the 6.14 cycle.
Is it because you don't have time this week or is it because you think it's
just too late to add code during the merge window? If it's the former, then
sure, we can wait. But if you want to wait just because we are in the merge
window, you don't need to. For things that add testing, it's OK to send
even this late in the game. What I and many should not accept, is any
active development on the kernel itself. Adding a sample module to be able
to test if things are working properly does not fall under that category.
The reason I ask, is I feel nervous about sending code to Linus that I
personally do not test. It's not a show stopper. I'll still send your
patches without or without this change. Before I send a pull request to
Linus, I like to run one last smoke test on the code, and that's when I
discovered I don't really have any tests to test your code.
-- Steve
next prev parent reply other threads:[~2024-11-19 15:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202411181440.qEdcuyh6-lkp@intel.com>
2024-11-18 20:27 ` [PATCH RESEND] jump_label: rust: pass a mut ptr to `static_key_count` Alice Ryhl
2024-11-18 20:41 ` Miguel Ojeda
2024-11-18 23:28 ` Steven Rostedt
2024-11-19 8:36 ` Alice Ryhl
2024-11-19 15:12 ` Steven Rostedt
2024-11-19 15:31 ` Alice Ryhl
2024-11-19 15:53 ` Steven Rostedt [this message]
2024-11-19 16:16 ` Alice Ryhl
2024-11-19 16:52 ` Steven Rostedt
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=20241119105347.32cbd654@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=aliceryhl@google.com \
--cc=boqun.feng@gmail.com \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ojeda@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox