From: Dmitrii Dolgov <9erthalion6@gmail.com>
To: linux-perf-users@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>, Miguel Ojeda <ojeda@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Dmitrii Dolgov <9erthalion6@gmail.com>,
kernel test robot <lkp@intel.com>
Subject: [PATCH v1] perf tests workload: Formatting for code_with_type.rs
Date: Mon, 9 Feb 2026 15:05:32 +0100 [thread overview]
Message-ID: <20260209140533.194251-1-9erthalion6@gmail.com> (raw)
One part of the rust code for code_with_type workload wasn't properly
formatted. Pass it through rustfmt to fix that.
Reported-by: kernel test robot <lkp@intel.com>
Closes: https://lore.kernel.org/oe-kbuild-all/202602091357.oyRv6hgQ-lkp@intel.com/
Signed-off-by: Dmitrii Dolgov <9erthalion6@gmail.com>
---
tools/perf/tests/workloads/code_with_type.rs | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/tools/perf/tests/workloads/code_with_type.rs b/tools/perf/tests/workloads/code_with_type.rs
index 3b91e51919d..3dab39b22dd 100644
--- a/tools/perf/tests/workloads/code_with_type.rs
+++ b/tools/perf/tests/workloads/code_with_type.rs
@@ -10,7 +10,11 @@ struct Buf {
#[no_mangle]
pub extern "C" fn test_rs(count: u32) {
- let mut b = Buf { data1: 0, data2: String::from("data"), data3: 0};
+ let mut b = Buf {
+ data1: 0,
+ data2: String::from("data"),
+ data3: 0,
+ };
for _ in 1..count {
b.data1 += 1;
base-commit: 335047109d7d488bf5ad32a4076e1a011994cd0e
--
2.52.0
next reply other threads:[~2026-02-09 14:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-09 14:05 Dmitrii Dolgov [this message]
2026-02-09 17:27 ` Ian Rogers
2026-02-10 8:56 ` Miguel Ojeda
2026-02-10 13:57 ` Mark Brown
2026-02-10 20:58 ` Arnaldo Carvalho de Melo
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=20260209140533.194251-1-9erthalion6@gmail.com \
--to=9erthalion6@gmail.com \
--cc=acme@kernel.org \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=lkp@intel.com \
--cc=namhyung@kernel.org \
--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
all inboxes | Powered by JetHome®