Re: [PATCH v1] perf tests workload: Formatting for code_with_type.rs

Re: [PATCH v1] perf tests workload: Formatting for code_with_type.rs

[Miguel Ojeda]

On Mon, Feb 9, 2026 at 3:05 PM Dmitrii Dolgov <9erthalion6@gmail.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@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202602091357.oyRv6hgQ-lkp@intel.com/
> Signed-off-by: Dmitrii Dolgov <9erthalion6@gmail.com>

Could this please be applied (or fixed in-place)?

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

Re: [PATCH v1] perf tests workload: Formatting for code_with_type.rs

[Mark Brown]

[-- Attachment #1: Type: text/plain, Size: 269 bytes --]

On Tue, Feb 10, 2026 at 09:56:36AM +0100, Miguel Ojeda wrote:

> Cc'ing Mark since I think the plan is to check in linux-next.

Yes, I was going to revisit this after the merge window - hopefully all
the fixes will have landed by then (clippy was the main thing IIRC).

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: [PATCH v1] perf tests workload: Formatting for code_with_type.rs

[Arnaldo Carvalho de Melo]

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@gmail.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@intel.com>
> > Closes: https://lore.kernel.org/oe-kbuild-all/202602091357.oyRv6hgQ-lkp@intel.com/
> > Signed-off-by: Dmitrii Dolgov <9erthalion6@gmail.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