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 v3] cfs-scheduler: Fixed "make check" warning in cfs_bandwidth01.c
Date: Fri, 12 Jun 2026 08:32:25 +0000 [thread overview]
Message-ID: <6a2bc41a.16c38fd9.38778b.a98a@mx.google.com> (raw)
In-Reply-To: <20260602100512.404810-1-samir@linux.ibm.com>
Merged, Thanks. I also fixed the commit message that was not
following the right conventions. Please make sure this will be
fixed the next time. In particular:
- commit subject was too long and verbose
- you added patch tracking into the commit message
Fixed into:
cfs-scheduler: Fixed "make check" warning
Fixed make check warning in cfs_bandwidth01.c to comply with LTP
coding style.
Regards,
--
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-06-12 8:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 10:05 [LTP] [PATCH v3] cfs-scheduler: Fixed "make check" warning in cfs_bandwidth01.c Samir
2026-06-02 11:24 ` [LTP] " linuxtestproject.agent
2026-06-12 8:28 ` [LTP] [PATCH v3] " Andrea Cervesato via ltp
2026-06-12 8:32 ` 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=6a2bc41a.16c38fd9.38778b.a98a@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 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.