From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: ltp@lists.linux.it, automated-testing@lists.yoctoproject.org
Subject: Re: [LTP] [PATCH v2 0/7] m4: Fix warnings, remove old checks
Date: Wed, 26 Jan 2022 19:14:57 +0100 [thread overview]
Message-ID: <YfGPoTFwN9r4f/UV@pevik> (raw)
In-Reply-To: <YfFn6DCo0ZHHXTI5@yuki>
Hi all,
[ Fixing the address: automated-testing@yoctoproject.org was wrong,
now using automated-testing@lists.yoctoproject.org ]
> Hi!
> Generally this is a nice cleanup, I guess that we should wait for a
> while if there is someone who will ask to keep the ltp-scanner and then
> we can go ahead with the changes...
+1. Please let us know if you're using ltp-scanner.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2022-01-26 18:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 12:35 [LTP] [PATCH v2 0/7] m4: Fix warnings, remove old checks Petr Vorel
2022-01-26 12:35 ` [LTP] [RFC PATCH v2 1/7] pan: Remove ltp-scanner Petr Vorel
2022-01-26 14:50 ` Cyril Hrubis
2022-01-27 8:38 ` Jan Stancek
2022-01-26 12:35 ` [LTP] [RFC PATCH v2 2/7] m4: Remove check for io_set_eventfd Petr Vorel
2022-01-26 14:55 ` Cyril Hrubis
2022-01-26 12:35 ` [LTP] [RFC PATCH v2 3/7] m4: Remove check for struct perf_event_attr Petr Vorel
2022-01-26 15:00 ` Cyril Hrubis
2022-01-26 12:35 ` [LTP] [RFC PATCH v2 4/7] realtime/m4: Simplify exp10 check Petr Vorel
2022-01-26 15:04 ` Cyril Hrubis
2022-01-26 22:30 ` Petr Vorel
2022-01-26 12:35 ` [LTP] [RFC PATCH v2 5/7] m4: Remove check for MREMAP_FIXED Petr Vorel
2022-01-26 15:15 ` Cyril Hrubis
2022-01-26 12:35 ` [LTP] [RFC PATCH v2 6/7] m4: Remove check for clone() supports 7 args Petr Vorel
2022-01-26 15:18 ` Cyril Hrubis
2022-01-26 12:35 ` [LTP] [RFC PATCH v2 7/7] m4: Fix warnings Petr Vorel
2022-01-26 15:23 ` Cyril Hrubis
2022-01-26 15:25 ` [LTP] [PATCH v2 0/7] m4: Fix warnings, remove old checks Cyril Hrubis
2022-01-26 18:14 ` Petr Vorel [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=YfGPoTFwN9r4f/UV@pevik \
--to=pvorel@suse.cz \
--cc=automated-testing@lists.yoctoproject.org \
--cc=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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.