Searched full:find (Results 1 – 25 of 521) sorted by relevance
12345678910>>...21
| /Documentation/core-api/ |
| D | union_find.rst | 4 Union-Find in Linux 11 What is union-find, and what is it used for? 14 Union-find is a data structure used to handle the merging and querying 15 of disjoint sets. The primary operations supported by union-find are: 20 Find: Determine which set a particular element belongs to, usually by 26 As a data structure used to maintain sets (groups), union-find is commonly 30 network routing. Consequently, union-find is widely referenced. Additionally, 31 union-find has applications in symbolic computation, register allocation, 37 the find operation, and using union by rank can reduce the time complexity 39 complexity of each find and union operation to O(α(n)), where α(n) is the [all …]
|
| D | printk-index.rst | 28 The printk index helps to find changes in the message formats. Also it helps 67 The extra information makes it a bit harder to find differences 70 it is the same string or find the commit that is responsible
|
| /Documentation/admin-guide/aoe/ |
| D | udev-install.sh | 7 # find udev.conf, often /etc/udev/udev.conf 8 # (or environment can specify where to find udev.conf) 14 conf="`find /etc -type f -name udev.conf 2> /dev/null`" 22 # find the directory where udev rules are stored, often 30 echo "$me Error: cannot find udev rules directory" 1>&2
|
| /Documentation/admin-guide/media/ |
| D | dvb_references.rst | 17 There, you'll find lots of information, from both development and usage 21 The API documentation is documented at the Kernel tree. You can find it 26 You may also find useful material at https://linuxtv.org/downloads/.
|
| D | faq.rst | 15 don't find an answer for your needs here, it is likely that 41 You can find more information at the LinuxTV wiki: 48 for example the ``dvbv5-scan`` tool. You can find more information 54 blind scan, trying hard to find all possible channels, but
|
| /Documentation/admin-guide/nfs/ |
| D | nfs-idmapper.rst | 41 uid: Find the UID for the given user 42 gid: Find the GID for the given group 43 user: Find the user name for the given UID 44 group: Find the group name for the given GID 57 request-key will find the first matching line and corresponding program. In
|
| /Documentation/networking/ |
| D | fib_trie.rst | 124 trie, key segment by key segment, until we find a leaf. check_leaf() does 127 If we find a match, we are done. 129 If we don't find a match, we enter prefix matching mode. The prefix length, 131 and we backtrack upwards through the trie trying to find a longest matching 137 the child index until we find a match or the child index consists of nothing but 141 chop off part of the key in order to find the longest matching prefix.
|
| /Documentation/admin-guide/laptops/ |
| D | sony-laptop.rst | 18 subsystem. See the logs of /proc/bus/input/devices to find out what those 30 If your laptop model supports it, you will find sysfs files in the 104 such a laptop you will find the necessary rfkill devices under 121 In your kernel logs you will find the list of all ACPI methods 128 (2) SN00 is used to find values in the lookup table 152 files and find out what is the impact on your laptop. 154 Should you find anything interesting, please report it back to me,
|
| /Documentation/ABI/testing/ |
| D | sysfs-devices | 12 this. If a program wishes to find different things in 17 devices being added and removed from this tree to find
|
| /Documentation/admin-guide/ |
| D | init.rst | 25 broken. Use ``readelf -d <INIT>|grep NEEDED`` to find out which libraries 35 execution. To find out more, add code ``to init/main.c`` to display 38 Please extend this explanation whenever you find new failure causes
|
| D | reporting-issues.rst | 15 you don't find any, install `the latest release from that series 26 don't find any to join, install `the latest mainline kernel 76 List (LKML) <https://lore.kernel.org/lkml/>`_. If you find matching reports, 106 Find out how and where its developers expect reports. Note: most of the 111 thoroughly for reports that might match your issue. If you find anything, 132 * Optimize your notes: try to find and write the most straightforward way to 139 decoding the kernel log to find the line of code that triggered the error. 220 scheduled for backporting already. If you don't find anything that way, 271 With that off the table, find below the details on how to properly report 333 List (LKML). If you find matching reports, join the discussion instead of [all …]
|
| /Documentation/sphinx/ |
| D | load_config.py | 25 start = config_file.find('Documentation/') 27 start = config_file.find('/', start + 1) 38 if l[0].find(dir + '/') == 0:
|
| /Documentation/filesystems/nfs/ |
| D | exporting.rst | 21 string for any dentry, and how to find an appropriate dentry for any 127 to find or create a dentry for the same object. 130 Given a filehandle fragment, this should find the implied object and 134 Given a filehandle fragment, this should find the parent of the 147 When given a parent dentry and a child dentry, this should find a name 151 to find potential names, and matches inode numbers to find the correct
|
| /Documentation/devicetree/bindings/soc/fsl/cpm_qe/cpm/ |
| D | i2c.txt | 16 i2c drivers to find the bus to probe: 20 by legacy i2c device drivers to find a bus in a specific context like
|
| /Documentation/translations/zh_CN/dev-tools/ |
| D | gcov.rst | 226 find $KSRC $KOBJ \( -name '*.gcno' -o -name '*.[ch]' -o -type l \) -a \ 257 find $GCDA -type d -exec mkdir -p $TEMPDIR/\{\} \; 258 find $GCDA -name '*.gcda' -exec sh -c 'cat < $0 > '$TEMPDIR'/$0' {} \; 259 find $GCDA -name '*.gcno' -exec sh -c 'cp -d $0 '$TEMPDIR'/$0' {} \;
|
| /Documentation/translations/zh_TW/dev-tools/ |
| D | gcov.rst | 226 find $KSRC $KOBJ \( -name '*.gcno' -o -name '*.[ch]' -o -type l \) -a \ 257 find $GCDA -type d -exec mkdir -p $TEMPDIR/\{\} \; 258 find $GCDA -name '*.gcda' -exec sh -c 'cat < $0 > '$TEMPDIR'/$0' {} \; 259 find $GCDA -name '*.gcno' -exec sh -c 'cp -d $0 '$TEMPDIR'/$0' {} \;
|
| /Documentation/arch/parisc/ |
| D | debugging.rst | 23 an HPMC instead of a kernel oops. To debug an HPMC, try to find 40 registers interruption handlers read to find out where the machine
|
| /Documentation/arch/arm/sunxi/ |
| D | clocks.rst | 50 you can find it at 55 released by Allwinner, you can find it at
|
| /Documentation/translations/ |
| D | index.rst | 43 translations' users should not find information that differs from the official 54 translations, you may find slight differences that carry the same message but
|
| /Documentation/RCU/ |
| D | rcu.rst | 72 for "read-copy update" to find it. 77 search for the string "Patent" in Documentation/RCU/RTFP.txt to find them. 89 - Where can I find more information on RCU?
|
| /Documentation/gpu/amdgpu/display/ |
| D | dc-glossary.rst | 6 component. If you do not find what you are looking for, look at the 7 'Documentation/gpu/amdgpu/amdgpu-glossary.rst'; if you cannot find it anywhere,
|
| /Documentation/doc-guide/ |
| D | contributing.rst | 18 general and find a place in the community. The bulk of what follows is the 142 run ``make refcheckdocs`` to find references to nonexistent documentation 150 this information harder to find and, for example, makes Sphinx unable to 155 The ``scripts/find-unused-docs.sh`` tool can be used to find these 213 Some documentation is beyond hope; we occasionally find documents that
|
| /Documentation/power/ |
| D | basic-pm-debugging.rst | 47 To find out why hibernation fails on your system, you can use a special testing 117 after the test, so please take that into consideration). To find this driver, 166 find it by loading a half of the modules you normally use and binary searching 174 Again, if you find the offending module(s), it(they) must be unloaded every time 209 techniques to find the problem. First, if there is a serial port in your box, 241 analogous to the one described in section 1. If you find some failing drivers,
|
| /Documentation/devicetree/bindings/usb/ |
| D | isp1301.txt | 8 - transceiver: phandle of isp1301 - this helps the ISP1301 driver to find the
|
| /Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-fm-rx.rst | 37 eight character text. However, it is also possible to find receivers 51 also possible to find receivers which can scroll strings sized as 32
|
12345678910>>...21