From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: Dmitrii Dolgov <9erthalion6@gmail.com>,
Mark Brown <broonie@kernel.org>,
linux-perf-users@vger.kernel.org,
Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>, Miguel Ojeda <ojeda@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
kernel test robot <lkp@intel.com>,
Linux-Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: [PATCH v1] perf tests workload: Formatting for code_with_type.rs
Date: Tue, 10 Feb 2026 17:58:54 -0300 [thread overview]
Message-ID: <aYucDuJDvxUBj79O@x1> (raw)
In-Reply-To: <CANiq72mW=hcvUGt=WENRiYVeVbb2bnYzizE00Eo-MW3b_MwRrg@mail.gmail.com>
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
prev parent reply other threads:[~2026-02-10 20:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-09 14:05 [PATCH v1] perf tests workload: Formatting for code_with_type.rs Dmitrii Dolgov
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 [this message]
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=aYucDuJDvxUBj79O@x1 \
--to=acme@kernel.org \
--cc=9erthalion6@gmail.com \
--cc=broonie@kernel.org \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=lkp@intel.com \
--cc=miguel.ojeda.sandonis@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.