Home
last modified time | relevance | path

Searched refs:EXPECT (Results 1 – 5 of 5) sorted by relevance

/linux-6.1.9/lib/
Dtest_memcat_p.c20 #define EXPECT (INPUT_MAX * 2 - 2) macro
76 if (i != EXPECT) { in test_memcat_p_init()
78 EXPECT, i); in test_memcat_p_init()
/linux-6.1.9/samples/bpf/
Dtest_lwt_bpf.sh115 EXPECT=$2
118 [ "$GOT" != "$EXPECT" ] && {
119 expect_fail "$EXPECT" "$GOT"
/linux-6.1.9/drivers/input/serio/
Dhil_mlc.c448 #define EXPECT(comp, to, got, got_wrong, timed_out) \ macro
475 EXPECT(HIL_ERR_INT | TEST_PACKET(0x5),
478 EXPECT(HIL_ERR_INT | TEST_PACKET(0xa),
493 EXPECT(HIL_PKT_CMD | HIL_CMD_IFC | HIL_ERR_INT,
550 EXPECT(HIL_PKT_CMD | HIL_CMD_POL | HIL_ERR_INT,
571 EXPECT(HIL_PKT_CMD | HIL_CMD_RPL | HIL_ERR_INT,
577 EXPECT(HIL_PKT_CMD | HIL_CMD_IFC | HIL_ERR_INT,
/linux-6.1.9/Documentation/devicetree/
Dof_unittest.rst27 2. Verbose Output (EXPECT)
36 'EXPECT \ : text' (begin) and 'EXPECT / : text' (end) messages have been
41 The EXPECT messages result in very noisy console messages that are difficult
/linux-6.1.9/Documentation/dev-tools/kunit/
Darchitecture.rst110 ``KUNIT_{EXPECT|ASSERT}_<op>[_MSG](kunit, property[, message])``
112 - ``{EXPECT|ASSERT}`` determines whether the check is an assertion or an