From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: "Samir Mulani" <samir@linux.ibm.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v6] sched/cfs-scheduler: Fix 'make check' errors and warnings in hackbench.c
Date: Tue, 25 Aug 2026 14:11:55 +0000 [thread overview]
Message-ID: <6a8da2ac.87996512.214a96.27cc@mx.google.com> (raw)
In-Reply-To: <20260821083736.49869-1-samir@linux.ibm.com>
Hi Samir,
mmh..I was about to merge this patch, but then I realized that
this was applied on a old API test, which is going to be
rewritten anyway into the new API. For this reason, I'm not
sure anymore if it's the case we are merging it.
Are you planning to rewrite the code into the new LTP API?
--
Andrea Cervesato
SUSE QE Automation Engineer Linux
andrea.cervesato@suse.com
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-08-25 14:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 8:37 [LTP] [PATCH v6] sched/cfs-scheduler: Fix 'make check' errors and warnings in hackbench.c Samir Mulani
2026-08-21 14:36 ` [LTP] " linuxtestproject.agent
2026-08-25 14:11 ` Andrea Cervesato via ltp [this message]
2026-09-10 17:17 ` [LTP] [PATCH v6] " Samir M
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=6a8da2ac.87996512.214a96.27cc@mx.google.com \
--to=ltp@lists.linux.it \
--cc=andrea.cervesato@suse.com \
--cc=samir@linux.ibm.com \
/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