* Re: [PATCH v1] perf tests workload: Formatting for code_with_type.rs
2026-02-10 8:56 ` [PATCH v1] perf tests workload: Formatting for code_with_type.rs Miguel Ojeda
@ 2026-02-10 13:57 ` Mark Brown
2026-02-10 20:58 ` Arnaldo Carvalho de Melo
1 sibling, 0 replies; 3+ messages in thread
From: Mark Brown @ 2026-02-10 13:57 UTC (permalink / raw)
To: Miguel Ojeda
Cc: Dmitrii Dolgov, Arnaldo Carvalho de Melo, linux-perf-users,
Namhyung Kim, Ian Rogers, Miguel Ojeda, Linux Kernel Mailing List,
kernel test robot, Linux-Next Mailing List
[-- 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 --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH v1] perf tests workload: Formatting for code_with_type.rs
2026-02-10 8:56 ` [PATCH v1] perf tests workload: Formatting for code_with_type.rs Miguel Ojeda
2026-02-10 13:57 ` Mark Brown
@ 2026-02-10 20:58 ` Arnaldo Carvalho de Melo
1 sibling, 0 replies; 3+ messages in thread
From: Arnaldo Carvalho de Melo @ 2026-02-10 20:58 UTC (permalink / raw)
To: Miguel Ojeda
Cc: Dmitrii Dolgov, Mark Brown, linux-perf-users, Namhyung Kim,
Ian Rogers, Miguel Ojeda, Linux Kernel Mailing List,
kernel test robot, Linux-Next Mailing List
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
^ permalink raw reply [flat|nested] 3+ messages in thread