From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: "Andrea Cervesato" <andrea.cervesato@suse.de>
Cc: Linux Test Project <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH] hugepages: ensure CONFIG_COMPACTION is defined
Date: Fri, 17 Jul 2026 06:49:11 +0000 [thread overview]
Message-ID: <6a59d068.b7086f8d.bdebb.42dc@mx.google.com> (raw)
In-Reply-To: <20260717-fix_tst_test_hugepages-v1-1-a63bf2ccdd17@suse.com>
I was not 100% sure to use kconfig or change the message, so I opted
for an hybrid approach (CONFIG_COMPACTION implies the missing file),
let me know if I should update the code or this is already ok.
Regards,
--
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-07-17 6:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 6:29 [LTP] [PATCH] hugepages: ensure CONFIG_COMPACTION is defined Andrea Cervesato
2026-07-17 6:49 ` Andrea Cervesato via ltp [this message]
2026-07-17 7:36 ` Li Wang
2026-07-17 7:45 ` Andrea Cervesato via ltp
2026-07-17 7:48 ` Cyril Hrubis
2026-07-17 9:34 ` Petr Vorel
2026-07-17 9:32 ` Petr Vorel
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=6a59d068.b7086f8d.bdebb.42dc@mx.google.com \
--to=ltp@lists.linux.it \
--cc=andrea.cervesato@suse.com \
--cc=andrea.cervesato@suse.de \
/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