From: Marius Kittler <mkittler@suse.de>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v5 3/4] Remove disabled code in ioctl02.c
Date: Tue, 19 Sep 2023 12:24:44 +0200 [thread overview]
Message-ID: <20230919102445.23934-4-mkittler@suse.de> (raw)
In-Reply-To: <20230919102445.23934-1-mkittler@suse.de>
Signed-off-by: Marius Kittler <mkittler@suse.de>
---
testcases/kernel/syscalls/ioctl/ioctl02.c | 14 --------------
1 file changed, 14 deletions(-)
diff --git a/testcases/kernel/syscalls/ioctl/ioctl02.c b/testcases/kernel/syscalls/ioctl/ioctl02.c
index b7548b4b3..b4db6ba86 100644
--- a/testcases/kernel/syscalls/ioctl/ioctl02.c
+++ b/testcases/kernel/syscalls/ioctl/ioctl02.c
@@ -148,20 +148,6 @@ static int chk_tty_parms(void)
termio.c_line);
flag++;
}
- /*
- * The following Code Sniffet is disabled to check the value of c_cflag
- * as it seems that due to some changes from 2.6.24 onwards, this
- * setting is not done properly for either of (B50|CS7|CREAD|PARENB|
- * PARODD|CLOCAL|(CREAD|HUPCL|CLOCAL).
- * However, it has been observed that other flags are properly set.
- */
-#if 0
- if (termio.c_cflag != (B50 | CS7 | CREAD | PARENB | PARODD | CLOCAL)) {
- tst_res(TINFO, "cflag has incorrect value. %o",
- termio.c_cflag);
- flag++;
- }
-#endif
for (i = 0; i < NCC; i++) {
if (i == VEOL2) {
--
2.42.0
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-09-19 10:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 10:24 [LTP] [PATCH v5 0/4] Improve ioctl02.c Marius Kittler
2023-09-19 10:24 ` [LTP] [PATCH v5 1/4] Refactor ioctl02.c to use the new test API Marius Kittler
2023-09-19 10:24 ` [LTP] [PATCH v5 2/4] Make checks for termio flags more strict Marius Kittler
2023-09-19 10:24 ` Marius Kittler [this message]
2023-09-19 10:24 ` [LTP] [PATCH v5 4/4] Use termios instead of legacy struct in ioctl02.c Marius Kittler
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=20230919102445.23934-4-mkittler@suse.de \
--to=mkittler@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox