From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: Samir <samir@linux.ibm.com>
Cc: Samir <samir@linux.ibm.com>, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2] cfs-scheduler: Fixed "make check" errors and warnings.
Date: Wed, 06 May 2026 14:56:11 +0000 [thread overview]
Message-ID: <69fb568e.050a0220.245213.1fc0@mx.google.com> (raw)
In-Reply-To: <20260412122842.1074017-1-samir@linux.ibm.com>
Hi Samir,
the AI agent didn't reply to your email at that time, but the
output is the following and I agree with that:
> Patch v1: https://lore.kernel.org/ltp/20260407062336.127454-1-samir@linux.ibm.com/
>
> Addressed review comments from patch v1 -> patch v2
> hackbench.c:
> - Drop SPDX-License-Identifier header addition.
> ...
Version changelog (v1->v2 notes, bullet lists, Patch vN links) must be
stripped before the final commit is applied. Move them to the cover
letter or drop them entirely.
[...]
> -/* This program is free software; you can redistribute it and/or modify */
> -/* it under the terms of the GNU General Public License as published by */
> -/* the Free Software Foundation; either version 2 of the License, or */
> -/* (at your option) any later version. */
The GPL license prose was removed but no SPDX header was added. Add
// SPDX-License-Identifier: GPL-2.0-or-later as the first line to
replace the boilerplate; do not leave the file without a license.
[...]
The cfs_bandwidth01.c and hackbench.c changes address different scopes
(one line vs. 13 style items). Consider splitting into two commits.
Regards,
LTP AI Reviewer
--
Andrea Cervesato
SUSE QE Automation Engineer Linux
andrea.cervesato@suse.com
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2026-05-06 14:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-12 12:28 [LTP] [PATCH v2] cfs-scheduler: Fixed "make check" errors and warnings Samir
2026-04-28 11:13 ` Samir M
2026-05-06 14:56 ` Andrea Cervesato via ltp [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=69fb568e.050a0220.245213.1fc0@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