linux-kernel - Re: [PATCH v1] perf tests workload: Formatting for code_with

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <aYucDuJDvxUBj79O@x1>
Date: Tue, 10 Feb 2026 17:58:54 -0300
From: Arnaldo Carvalho de Melo <acme@...nel.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
Cc: Dmitrii Dolgov <9erthalion6@...il.com>, Mark Brown <broonie@...nel.org>,
	linux-perf-users@...r.kernel.org,
	Namhyung Kim <namhyung@...nel.org>, Ian Rogers <irogers@...gle.com>,
	Miguel Ojeda <ojeda@...nel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	kernel test robot <lkp@...el.com>,
	Linux-Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: [PATCH v1] perf tests workload: Formatting for code_with_type.rs

On Tue, Feb 10, 2026 at 09:56:36AM +0100, Miguel Ojeda wrote:
> On Mon, Feb 9, 2026 at 3:05 PM Dmitrii Dolgov <9erthalion6@...il.com> wrote:
> >
> > 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@...el.com>
> > Closes: https://lore.kernel.org/oe-kbuild-all/202602091357.oyRv6hgQ-lkp@intel.com/
> > Signed-off-by: Dmitrii Dolgov <9erthalion6@...il.com>
> 
> Could this please be applied (or fixed in-place)?

Its merged and pushed out, should be clean now,

- Arnaldo
 
> It is now in next-20260209, and we check this in different CIs. It
> also makes LKP give spurious reports, e.g.:
> 
>   https://lore.kernel.org/all/202602100751.ldfRitCJ-lkp@intel.com/
> 
> Thanks!
> 
> Fixes: 2e05bb52a12d ("perf test workload: Add code_with_type test workload")
> 
> Cc'ing Mark since I think the plan is to check in linux-next.
> 
> Cheers,
> Miguel