From: Cyril Hrubis <chrubis@suse.cz>
To: Hongchen Zhang <zhanghongchen@loongson.cn>
Cc: ltp@lists.linux.it, Lingling Li <lilingling@loongson.cn>
Subject: Re: [LTP] [PATCH v4 2/2] syslog11: save and restore console log level
Date: Tue, 19 Jul 2022 13:45:15 +0200 [thread overview]
Message-ID: <YtaZSygV7SkAcNsM@rei> (raw)
In-Reply-To: <1658228710-37206-2-git-send-email-zhanghongchen@loongson.cn>
Hi!
> Signed-off-by: Lingling Li <lilingling@loongson.cn>
> Signed-off-by: Hongchen Zhang <zhanghongchen@loongson.cn>
> ---
> testcases/kernel/syscalls/syslog/syslog11.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/testcases/kernel/syscalls/syslog/syslog11.c b/testcases/kernel/syscalls/syslog/syslog11.c
> index 8a19a2a..e60bd2b 100644
> --- a/testcases/kernel/syscalls/syslog/syslog11.c
> +++ b/testcases/kernel/syscalls/syslog/syslog11.c
> @@ -57,6 +57,10 @@ static void run(unsigned int n)
>
> static struct tst_test test = {
> .test = run,
> + .save_restore = (const struct tst_path_val[]) {
> + {"!/proc/sys/kernel/printk", NULL},
> + {NULL, NULL}
I've changed this {NULL, NULL} to just {} in order to fix warnings
reported by 'make check-syslog11' and pushed, thanks.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-07-19 11:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 11:05 [LTP] [PATCH v4 1/2] syslog11: convert to new LTP API Hongchen Zhang
2022-07-19 11:05 ` [LTP] [PATCH v4 2/2] syslog11: save and restore console log level Hongchen Zhang
2022-07-19 11:45 ` Cyril Hrubis [this message]
2022-07-19 11:42 ` [LTP] [PATCH v4 1/2] syslog11: convert to new LTP API Cyril Hrubis
2022-07-19 11:54 ` Hongchen Zhang
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=YtaZSygV7SkAcNsM@rei \
--to=chrubis@suse.cz \
--cc=lilingling@loongson.cn \
--cc=ltp@lists.linux.it \
--cc=zhanghongchen@loongson.cn \
/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