| /Linux-v6.1/scripts/kconfig/tests/err_recursive_dep/ |
| D | expected_stderr | 1 Kconfig:11:error: recursive dependency detected!
4 subsection "Kconfig recursive dependency limitations"
6 Kconfig:5:error: recursive dependency detected!
9 subsection "Kconfig recursive dependency limitations"
11 Kconfig:17:error: recursive dependency detected!
15 subsection "Kconfig recursive dependency limitations"
17 Kconfig:32:error: recursive dependency detected!
21 subsection "Kconfig recursive dependency limitations"
23 Kconfig:37:error: recursive dependency detected!
27 subsection "Kconfig recursive dependency limitations"
[all …]
|
| /Linux-v6.1/Documentation/locking/ |
| D | lockdep-design.rst | 405 spin_lock() or write_lock()), non-recursive readers (i.e. shared lockers, like
406 down_read()) and recursive readers (recursive shared lockers, like rcu_read_lock()).
410 r: stands for non-recursive readers.
411 R: stands for recursive readers.
412 S: stands for all readers (non-recursive + recursive), as both are shared lockers.
413 N: stands for writers and non-recursive readers, as both are not recursive.
421 While non-recursive readers will cause a self deadlock if trying to acquire inside
424 The difference between recursive readers and non-recursive readers is because:
425 recursive readers get blocked only by a write lock *holder*, while non-recursive
435 Task A gets the reader (no matter whether recursive or non-recursive) on X via
[all …]
|
| D | pi-futex.rst | 18 recursive locking, etc.
|
| /Linux-v6.1/Documentation/kbuild/ |
| D | Kconfig.recursion-issue-01 | 1 # Simple Kconfig recursive issue
8 # This Kconfig file has a simple recursive dependency issue. In order to
9 # understand why this recursive dependency issue occurs lets consider what
34 # the "recursive dependency detected" error.
41 # implications of this recursive issue where the solution is perhaps not so
43 # CORE also consist of a solution to this recursive problem.
45 mainmenu "Simple example to demo kconfig recursive dependency issue"
|
| D | Kconfig.recursion-issue-02 | 1 # Cumulative Kconfig recursive issue
8 # The recursive limitations with Kconfig has some non intuitive implications on
10 # of the recursive limitation is that drivers cannot negate features from other
47 mainmenu "Simple example to demo cumulative kconfig recursive dependency implication"
|
| D | kconfig-language.rst | 576 Kconfig recursive dependency limitations
579 If you've hit the Kconfig error: "recursive dependency detected" you've run
580 into a recursive dependency issue with Kconfig, a recursive dependency can be
586 Kconfig recursive issue" subsection below. Kconfig does not do recursive
593 Simple Kconfig recursive issue
602 Cumulative Kconfig recursive issue
611 Practical solutions to kconfig recursive issue
614 Developers who run into the recursive Kconfig issue have two options
634 Below is a list of examples of prior fixes for these types of recursive issues;
676 the current known recursive dependency issues. It is not known if this would
[all …]
|
| /Linux-v6.1/scripts/gdb/linux/ |
| D | device.py | 90 def _show_device(dev, level=0, recursive=False): argument
92 if recursive:
94 _show_device(child, level + 1, recursive)
147 _show_device(dev, level=0, recursive=True)
|
| /Linux-v6.1/scripts/dtc/ |
| D | dt-extract-compatibles | 64 for filename in glob.iglob(f + "/**/*.c", recursive=True):
|
| /Linux-v6.1/tools/perf/util/ |
| D | dwarf-aux.c | 767 bool recursive; member
788 if (!lw->recursive) in __die_walk_funclines_cb()
806 static int __die_walk_funclines(Dwarf_Die *sp_die, bool recursive, in __die_walk_funclines() argument
810 .recursive = recursive, in __die_walk_funclines()
|
| /Linux-v6.1/tools/testing/selftests/cgroup/ |
| D | memcg_protection.m | 54 % recursive protection
|
| /Linux-v6.1/Documentation/admin-guide/sysctl/ |
| D | user.rst | 33 This recursive counting of created objects ensures that creating a
|
| /Linux-v6.1/security/tomoyo/ |
| D | util.c | 867 goto recursive; in tomoyo_path_matches_pattern2()
883 recursive: in tomoyo_path_matches_pattern2()
|
| /Linux-v6.1/Documentation/filesystems/ |
| D | ceph.rst | 60 Ceph also provides some recursive accounting on directories for nested
65 no 'du' or similar recursive scan of the file system is required.
|
| D | path-lookup.txt | 60 name in the name string, and require some recursive path walking. Mount points
|
| /Linux-v6.1/include/sound/ |
| D | hda_codec.h | 362 hda_nid_t nid, int recursive);
|
| /Linux-v6.1/lib/ |
| D | Kconfig.kgdb | 38 difficult to inadvertently provoke recursive trap handling.
|
| D | Kconfig | 493 modify. The algorithms are non-recursive, and the trees are highly
|
| /Linux-v6.1/sound/pci/hda/ |
| D | hda_codec.c | 265 hda_nid_t nid, int recursive) in snd_hda_get_conn_index() argument
274 if (!recursive) in snd_hda_get_conn_index()
276 if (recursive > 10) { in snd_hda_get_conn_index()
280 recursive++; in snd_hda_get_conn_index()
285 if (snd_hda_get_conn_index(codec, conn[i], nid, recursive) >= 0) in snd_hda_get_conn_index()
|
| /Linux-v6.1/Documentation/trace/ |
| D | kprobes.rst | 130 For example, if the function is non-recursive and is called with a
132 non-recursive and can never relinquish the CPU (e.g., via a semaphore
299 (trapping) such functions can cause a recursive trap (e.g. double
|
| /Linux-v6.1/Documentation/ia64/ |
| D | mca.rst | 85 own stack as running on that cpu. Then a recursive error gets a
|
| /Linux-v6.1/Documentation/admin-guide/cgroup-v1/ |
| D | blkio-controller.rst | 247 same information as their non-recursive counterparts but
|
| /Linux-v6.1/Documentation/driver-api/rapidio/ |
| D | rapidio.rst | 254 The enumeration process traverses the network using a recursive depth-first
|
| /Linux-v6.1/Documentation/admin-guide/device-mapper/ |
| D | thin-provisioning.rst | 17 recursive snapshots (snapshots of snapshots of snapshots ...). The
|
| /Linux-v6.1/Documentation/core-api/ |
| D | printk-formats.rst | 455 Implements a "recursive vsnprintf".
|
| D | assoc_array.rst | 495 slot in that parent that points to it. None-recursive iteration uses these to
|
