| /freebsd/crypto/openssl/util/ |
| H A D | check-format-test-positives.c | 19 * a single flaw that should be reported. Normally it should be reported
32 /*@0 intra-line comment indent off by 1, reported unless sloppy-cmt */
33 /*X */ /*@2 missing spc or '*' after comment start reported unless sloppy-spc */
34 /* X*/ /*@ missing space before comment end , reported unless sloppy-spc */
37 …*@ above multi-line comment start indent off by 1, reported unless sloppy-cmt; this comment line i…
43 *X*@ no spc after leading '*' in multi-line comment, reported unless sloppy-spc
44 *@0 more than two spaces after . in comment, no more reported
45 *@0 more than two spaces after ? in comment, no more reported
46 *@0 more than two spaces after ! in comment, no more reported
50 /*@ comment line is 4 columns tooooooooooooooooo wide, reported unless sloppy-len */
[all …]
|
| /freebsd/contrib/libfido2/man/ |
| H A D | fido_cbor_info_new.3 | 252 length in bytes supported by the authenticator as reported in
258 a single credential ID list as reported in
264 as reported in
271 as reported in
281 serialized largeBlob array as reported in
287 authenticator as reported in
317 Predefined Values and reported in
334 authenticator as reported in
345 as reported in
|
| /freebsd/contrib/netbsd-tests/kernel/ |
| H A D | t_ptrace_wait.h | 226 ATF_REQUIRE_MSG(WIFEXITED(status), "Reported !exited process"); in validate_status_exited()
227 ATF_REQUIRE_MSG(!WIFCONTINUED(status), "Reported continued process"); in validate_status_exited()
228 ATF_REQUIRE_MSG(!WIFSIGNALED(status), "Reported signaled process"); in validate_status_exited()
229 ATF_REQUIRE_MSG(!WIFSTOPPED(status), "Reported stopped process"); in validate_status_exited()
250 ATF_REQUIRE_MSG(!WIFEXITED(status), "Reported exited process"); in validate_status_continued()
251 ATF_REQUIRE_MSG(WIFCONTINUED(status), "Reported !continued process"); in validate_status_continued()
252 ATF_REQUIRE_MSG(!WIFSIGNALED(status), "Reported signaled process"); in validate_status_continued()
253 ATF_REQUIRE_MSG(!WIFSTOPPED(status), "Reported stopped process"); in validate_status_continued()
268 ATF_REQUIRE_MSG(!WIFEXITED(status), "Reported exited process"); in validate_status_signaled()
269 ATF_REQUIRE_MSG(!WIFCONTINUED(status), "Reported continued process"); in validate_status_signaled()
[all …]
|
| /freebsd/sys/contrib/openzfs/tests/zfs-tests/tests/functional/events/ |
| H A D | zed_cksum_reported.ksh | 30 # Verify that checksum errors are accurately reported to ZED
35 # 3. Verify checksum error count reported to ZED is not zero
62 log_assert "Test reported checksum errors to ZED"
90 # checksum error as reported from the vdev.
93 # first checksum error reported to ZED.
125 log_pass "Test reported checksum errors to ZED"
|
| /freebsd/sys/contrib/zstd/ |
| H A D | CHANGELOG | 201 api: fixed ZSTD_initCStream_advanced() performance with fast modes, reported by @QrczakMK
209 cli: fix command `-D dictionary` on Windows, reported by @artyompetrov
212 build: fixed zlibWrapper compilation on Visual Studio, reported by @bluenlive
213 build: fixed deprecation warning for certain gcc version, reported by @jasonma163
305 build: fix compilation on MIPS32, reported by @clbr (#1441)
333 api : fix : block api can be streamed with > 4 GB, reported by @catid
376 fix : bug #944 : multithreading with shared ditionary and large data, reported by @gsliepen
383 build: fix : compilation under rhel6 and centos6, reported by @pixelb
398 cli : fix : do not change /dev/null permissions when using command -t with root access, reported by…
403 build: fix : no-multithread variant compiles without pool.c dependency, reported by Mitchell Blank …
[all …]
|
| /freebsd/sys/contrib/openzfs/tests/zfs-tests/tests/functional/fallocate/ |
| H A D | fallocate_zero-range.ksh | 40 # Note: We can't compare exact block numbers as reported by du, because
89 # Zero a range covering the first full block. The reported size should decrease.
95 # Partially zero a range in the second block. The reported size should
102 # Zero range which overlaps the third and fourth block. The reported size
110 # The reported size should decrease, and the apparent file size must not
121 # with PUNCH_HOLE. The reported size should remain constant.
|
| H A D | fallocate_punch-hole.ksh | 40 # Note: We can't compare exact block numbers as reported by du, because
98 # Punch a hole for the first full block. The reported size should decrease.
104 # Partially punch a hole in the second block. The reported size should
111 # Punch a hole which overlaps the third and fourth block. The reported size
118 # Punch a hole from the fifth block past the end of file. The reported size
|
| /freebsd/sys/contrib/device-tree/Bindings/input/touchscreen/ |
| H A D | touchscreen.yaml | 21 description: minimum x coordinate reported
26 description: minimum y coordinate reported
31 description: horizontal resolution of touchscreen (maximum x coordinate reported + 1)
35 description: vertical resolution of touchscreen (maximum y coordinate reported + 1)
39 description: maximum reported pressure (arbitrary range dependent on the controller)
|
| /freebsd/contrib/ntp/sntp/libevent/ |
| H A D | ChangeLog-1.4 | 24 o Fix memory leak when setting up priorities; reported by Alexander Drozdov (cb1a722)
35 o Do not drop data from evbuffer when out of memory; reported by Jacek Masiulaniec
36 …o Rename our replacement compat/sys/_time.h header to avoid build a conflict on HPUX; reported by …
59 o clean up buffered http connection data on reset; reported by Brian O'Kelley
65 o off-by-one error in epoll_recalc; reported by Victor Goya
71 o Clear the timer cache on entering the event loop; reported by Victor Chang
72 o Only bind the socket on connect when a local address has been provided; reported by Alejo Sanchez
74 o Clear the timer cache when leaving the event loop; reported by Robin Haberkorn
75 o Fix a typo in setting the global event base; reported by lance.
99 o Fix a memory leak when using signals for some event bases; reported by Alexander Drozdov.
[all …]
|
| /freebsd/contrib/libevent/ |
| H A D | ChangeLog-1.4 | 24 o Fix memory leak when setting up priorities; reported by Alexander Drozdov (cb1a722)
35 o Do not drop data from evbuffer when out of memory; reported by Jacek Masiulaniec
36 …o Rename our replacement compat/sys/_time.h header to avoid build a conflict on HPUX; reported by …
59 o clean up buffered http connection data on reset; reported by Brian O'Kelley
65 o off-by-one error in epoll_recalc; reported by Victor Goya
71 o Clear the timer cache on entering the event loop; reported by Victor Chang
72 o Only bind the socket on connect when a local address has been provided; reported by Alejo Sanchez
74 o Clear the timer cache when leaving the event loop; reported by Robin Haberkorn
75 o Fix a typo in setting the global event base; reported by lance.
99 o Fix a memory leak when using signals for some event bases; reported by Alexander Drozdov.
[all …]
|
| /freebsd/contrib/kyua/integration/ |
| H A D | cmd_about_test.sh | 42 atf_fail 'No version reported'
43 grep 'Copyright' "${file}" || atf_fail 'No license reported'
44 grep '^\*[^<>]*$' "${file}" || atf_fail 'No authors reported'
45 grep '^\*.*<.*@.*>$' "${file}" || atf_fail 'No contributors reported'
46 grep 'Homepage' "${file}" || atf_fail 'No homepage reported'
|
| /freebsd/sys/dev/hid/ |
| H A D | hmt.c | 99 bool reported; /* Item value is passed to evdev */ member
107 .reported = false,
113 .reported = true,
119 .reported = true,
125 .reported = true,
131 .reported = true,
137 .reported = true,
143 .reported = true,
149 .reported = true,
155 .reported = true,
[all …]
|
| /freebsd/contrib/llvm-project/llvm/lib/IR/ |
| H A D | PrintPasses.cpp | 38 // make changes to the IR are reported as not making any changes. In addition,
39 // the initial IR is also reported. Other hidden options affect the output from
41 // actually change the IR and other passes are reported as filtered out. The
42 // specified passes will either be reported as making no changes (with no IR
43 // reported) or the changed IR will be reported. Also, the -filter-print-funcs
48 // for certain passes on certain functions to be reported in different formats,
49 // with the rest being reported as filtered out. The -print-before-changed
|
| /freebsd/lib/libpmc/pmu-events/arch/x86/tigerlake/ |
| H A D | memory.json | 35 … latency from first dispatch to completion is greater than 128 cycles. Reported latency may be lo…
51 …e latency from first dispatch to completion is greater than 16 cycles. Reported latency may be lo…
67 … latency from first dispatch to completion is greater than 256 cycles. Reported latency may be lo…
83 …e latency from first dispatch to completion is greater than 32 cycles. Reported latency may be lo…
99 …he latency from first dispatch to completion is greater than 4 cycles. Reported latency may be lo…
115 … latency from first dispatch to completion is greater than 512 cycles. Reported latency may be lo…
131 …e latency from first dispatch to completion is greater than 64 cycles. Reported latency may be lo…
147 …he latency from first dispatch to completion is greater than 8 cycles. Reported latency may be lo…
|
| /freebsd/sys/contrib/device-tree/Bindings/arm/tegra/ |
| H A D | nvidia,tegra194-cbb.yaml | 18 This driver handles errors due to illegal register accesses reported
26 SError or Data Abort is masked and the error is reported with interrupt.
29 errors due to illegal accesses from CCPLEX are reported by interrupts.
30 If ERD is not set, then error is reported by SError.
|
| /freebsd/sys/dev/usb/input/ |
| H A D | wmt.c | 114 bool reported; /* Item value is passed to evdev */ member
122 .reported = false,
128 .reported = true,
134 .reported = true,
140 .reported = true,
146 .reported = true,
152 .reported = true,
158 .reported = true,
164 .reported = true,
170 .reported = true,
[all …]
|
| /freebsd/contrib/ofed/librdmacm/man/ |
| H A D | rdma_accept.3 | 33 communication request. Users should use the rdma_conn_param values reported
40 If the conn_param parameter is NULL, the values reported in the connection
55 value reported in the connect request event.
60 max_qp_init_rd_atom and the initiator_depth value reported in the connect
|
| /freebsd/lib/libdevstat/ |
| H A D | devstat.3 | 566 This number is in terms of the blocksize reported by the device.
567 If no blocksize has been reported (i.e., the block size is 0), a default
579 This number is in terms of the blocksize reported by the device.
580 If no blocksize has been reported (i.e., the block size is 0), a default
649 This number is in terms of the blocksize reported by the device.
650 If no blocksize has been reported (i.e., the block size is 0), a default
663 This number is in terms of the blocksize reported by the device.
664 If no blocksize has been reported (i.e., the block size is 0), a default
|
| /freebsd/contrib/llvm-project/lldb/include/lldb/Core/ |
| H A D | Progress.h | 31 /// The Progress class helps make sure that progress is correctly reported
34 /// completed update is reported even if the user doesn't explicitly cause one
37 /// The progress is reported via a callback whose type is ProgressCallback:
74 /// items being reported on.
81 /// progress is to be reported only to specific debuggers.
133 /// Set to true when progress has been reported where m_completed == m_total
|
| /freebsd/usr.bin/mt/ |
| H A D | mt.1 | 120 number reported is specific for that hardware only.
148 is enabled is reported.
150 it is doing with the device) is reported.
217 is enabled is reported.
219 it is doing with the device) is reported.
225 READ POSITION command, the Reported File Number and Reported Record Number
226 will be numbers other than -1, and there may be Flags reported as well.
237 Note that the Reported Record Number is the tape block or object number
244 The Reported File and Record Numbers are definitive, if they are numbers
257 reported by
[all …]
|
| /freebsd/contrib/kyua/engine/ |
| H A D | atf_result_test.cpp | 377 "Expected failure should have reported success but " in ATF_TEST_CASE_BODY()
382 "Expected failure should have reported success but " in ATF_TEST_CASE_BODY()
387 "Expected failure should have reported success but " in ATF_TEST_CASE_BODY()
479 "Failed test case should have reported failure but " in ATF_TEST_CASE_BODY()
484 "Failed test case should have reported failure but " in ATF_TEST_CASE_BODY()
489 "Failed test case should have reported failure but " in ATF_TEST_CASE_BODY()
514 "Passed test case should have reported success but " in ATF_TEST_CASE_BODY()
519 "Passed test case should have reported success but " in ATF_TEST_CASE_BODY()
524 "Passed test case should have reported success but " in ATF_TEST_CASE_BODY()
549 "Skipped test case should have reported success but " in ATF_TEST_CASE_BODY()
[all …]
|
| /freebsd/contrib/libpcap/doc/ |
| H A D | README.linux | 29 Statistics reported by pcap are platform specific. The statistics
30 reported by pcap_stats on Linux are as follows:
36 but won't be reported by, for example, tcpdump output.
|
| /freebsd/sys/contrib/device-tree/Bindings/serial/ |
| H A D | snps-dw-apb-uart.yaml | 109 always be reported as active instead of being obtained from the modem
116 always be reported as active instead of being obtained from the modem
123 always be reported as active instead of being obtained from the modem
130 be reported as inactive instead of being obtained from the modem status
|
| /freebsd/share/man/man9/ |
| H A D | mod_cc.9 | 154 The ACK types currently reported by the stack are CC_ACK and CC_DUPACK.
165 The congestion event types currently reported by the stack are CC_ECN, CC_RTO,
167 CC_ECN is reported when the TCP stack receives an explicit congestion notification
169 CC_RTO is reported when the retransmission time out timer fires.
170 CC_RTO_ERR is reported if the retransmission time out timer fired in error.
171 CC_NDUPACK is reported if N duplicate ACKs have been received back-to-back,
|
| /freebsd/lib/libpmc/pmu-events/arch/x86/sapphirerapids/ |
| H A D | memory.json | 79 … latency from first dispatch to completion is greater than 128 cycles. Reported latency may be lo…
95 …e latency from first dispatch to completion is greater than 16 cycles. Reported latency may be lo…
111 … latency from first dispatch to completion is greater than 256 cycles. Reported latency may be lo…
127 …e latency from first dispatch to completion is greater than 32 cycles. Reported latency may be lo…
143 …he latency from first dispatch to completion is greater than 4 cycles. Reported latency may be lo…
159 … latency from first dispatch to completion is greater than 512 cycles. Reported latency may be lo…
175 …e latency from first dispatch to completion is greater than 64 cycles. Reported latency may be lo…
191 …he latency from first dispatch to completion is greater than 8 cycles. Reported latency may be lo…
|