Searched full:parse (Results 1 – 25 of 95) sorted by relevance
1234
| /Documentation/driver-api/mmc/ |
| D | mmc-tools.rst | 15 - Print and parse extcsd data.
35 - Print and parse CID data.
36 - Print and parse CSD data.
37 - Print and parse SCR data.
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-uacce | 6 Can be any string and up to userspace to parse.
45 Can be any string and up to userspace to parse.
|
| D | sysfs-bus-event_source-devices-caps | 24 the perf tool to parse the logged counters in each branch.
|
| /Documentation/dev-tools/kunit/ |
| D | architecture.rst | 160 is used to configure, build, execute, parse test results and run all of the
161 previous commands in correct order (i.e., configure, build, execute and parse).
163 enabled and manually parse the results (see
190 output (stdout), and passes them to ``parse`` to be parsed.
194 - ``parse`` extracts the KTAP output from a kernel log, parses
|
| D | run_wrapper.rst | 8 manually, and then use kunit_tool to parse the results. To run tests
143 If we have KUnit results in the raw TAP format, we can parse them and
144 print the human-readable summary with the ``parse`` command for
151 ./tools/testing/kunit/kunit.py parse /var/log/dmesg
153 dmesg | ./tools/testing/kunit/kunit.py parse
|
| D | running_tips.rst | 18 ( cd "$(git rev-parse --show-toplevel)" && ./tools/testing/kunit/kunit.py run "$@" )
214 failed (as of 5.13). But ``kunit.py parse`` would, see below.
227 You can use ``kunit.py parse`` to parse dmesg for test output and print out
232 $ ./tools/testing/kunit/kunit.py parse /var/log/dmesg
|
| D | faq.rst | 79 can run it manually against ``stdin`` or a file with ``kunit.py parse``.)
101 can be parsed with ``kunit.py parse``. For more details, see :ref:`kunit-on-qemu`.
|
| /Documentation/networking/ |
| D | strparser.rst | 14 Connection Multiplexor (KCM) uses the Stream Parser to parse messages
89 parse an sk_buff. The number of bytes processed or a negative
92 parser will parse. timeo is timeout for completing a message.
123 should parse the sk_buff as containing the headers for the
134 0 indicates more data must be received to parse the message
|
| /Documentation/userspace-api/media/v4l/ |
| D | pixfmt-compressed.rst | 47 then the decoder has no requirements since it can parse all the
103 then the decoder has no requirements since it can parse all the
112 then the decoder has no requirements since it can parse all the
203 then the decoder has no requirements since it can parse all the
231 since the decoder can parse all the information from the raw bytestream.
|
| /Documentation/translations/zh_CN/doc-guide/ |
| D | index.rst | 18 parse-headers
|
| D | parse-headers.rst | 5 :Original: Documentation/doc-guide/parse-headers.rst
|
| /Documentation/doc-guide/ |
| D | index.rst | 12 parse-headers
|
| /Documentation/userspace-api/media/ |
| D | Makefile | 6 PARSER = $(srctree)/Documentation/sphinx/parse-headers.pl
19 quiet_gen_rst = echo ' PARSE $(patsubst $(srctree)/%,%,$<)'; \
|
| /Documentation/driver-api/pldmfw/ |
| D | index.rst | 28 ``pldmfw`` implements logic to parse the packed binary format of the PLDM
60 1. Parse the firmware file for record and component information
|
| /Documentation/translations/it_IT/doc-guide/ |
| D | index.rst | 17 parse-headers
|
| /Documentation/arch/x86/ |
| D | booting-dt.rst | 18 does not parse / consider data which is already covered by the boot
|
| /Documentation/ |
| D | dontdiff | 193 parse.c
194 parse.h
|
| /Documentation/ABI/stable/ |
| D | vdso | 20 To find the DSO, parse the auxiliary vector passed to the program's
|
| D | sysfs-firmware-opal-elog | 32 do not parse this at all in kernel, leaving it up to
|
| /Documentation/crypto/ |
| D | asymmetric-keys.rst | 50 the opportunity to pre-parse a key and to determine the description the key
233 blob of data that holds the key data. It would have to parse it and error
263 int (*parse)(struct key_preparsed_payload *prep);
272 1) parse().
292 size. The parse() function is not permitted to change these two values at
|
| /Documentation/sphinx/ |
| D | parse-headers.pl | 185 die "Can't parse $file_exceptions: $_";
224 die "Can't parse $file_exceptions: $_";
340 parse_headers.pl - parse a C file, in order to identify functions, structs,
385 Please read Documentation/doc-guide/parse-headers.rst at the Kernel's
|
| /Documentation/hid/ |
| D | hidreport-parsing.rst | 17 and try to parse it by hand.
|
| /Documentation/trace/postprocess/ |
| D | trace-vmscan-postprocess.pl | 103 # Parse command line options
310 print "WARNING: Failed to parse mm_vmscan_direct_reclaim_begin as expected\n";
333 print "WARNING: Failed to parse mm_vmscan_kswapd_wake as expected\n";
367 print "WARNING: Failed to parse mm_vmscan_wakeup_kswapd as expected\n";
377 print "WARNING: Failed to parse mm_vmscan_lru_isolate as expected\n";
398 print "WARNING: Failed to parse mm_vmscan_lru_shrink_inactive as expected\n";
419 print "WARNING: Failed to parse mm_vmscan_writepage as expected\n";
|
| /Documentation/admin-guide/ |
| D | dynamic-debug-howto.rst | 71 dyndbg: query parse failed
154 file inode.c:start_* # parse :tail as a func (above)
155 file inode.c:1-100 # parse :tail as a line-range (above)
|
| /Documentation/driver-api/ |
| D | pwrseq.rst | 84 consumer driver controls one of its modules, the provider driver may parse the
|
1234