Searched refs:EXPECT (Results 1 – 6 of 6) sorted by relevance
| /linux-5.19.10/lib/ |
| D | test_memcat_p.c | 20 #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-5.19.10/samples/bpf/ |
| D | test_lwt_bpf.sh | 115 EXPECT=$2
118 [ "$GOT" != "$EXPECT" ] && {
119 expect_fail "$EXPECT" "$GOT"
|
| /linux-5.19.10/drivers/input/serio/ |
| D | hil_mlc.c | 448 #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-5.19.10/Documentation/devicetree/ |
| D | of_unittest.rst | 27 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-5.19.10/tools/perf/pmu-events/ |
| D | jevents.c | 274 #define EXPECT(e, t, m) do { if (!(e)) { \ macro
539 EXPECT(tokens->type == JSMN_ARRAY, tokens, "expected top level array"); in json_events()
563 EXPECT(obj->type == JSMN_OBJECT, obj, "expected object"); in json_events()
570 EXPECT(field->type == JSMN_STRING, tok + j, in json_events()
573 EXPECT(val->type == JSMN_STRING, tok + j + 1, in json_events()
761 EXPECT(tok - tokens == len, tok, "unexpected objects at end"); in json_events()
|
| /linux-5.19.10/Documentation/dev-tools/kunit/ |
| D | architecture.rst | 110 ``KUNIT_{EXPECT|ASSERT}_<op>[_MSG](kunit, property[, message])``
112 - ``{EXPECT|ASSERT}`` determines whether the check is an assertion or an
|