Home
last modified time | relevance | path

Searched refs:recursive (Results 1 – 25 of 30) sorted by relevance

12

/Linux-v5.4/scripts/kconfig/tests/err_recursive_dep/
Dexpected_stderr1 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-v5.4/Documentation/kbuild/
DKconfig.recursion-issue-011 # 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"
DKconfig.recursion-issue-021 # 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"
Dkconfig-language.rst538 Kconfig recursive dependency limitations
541 If you've hit the Kconfig error: "recursive dependency detected" you've run
542 into a recursive dependency issue with Kconfig, a recursive dependency can be
548 Kconfig recursive issue" subsection below. Kconfig does not do recursive
555 Simple Kconfig recursive issue
564 Cumulative Kconfig recursive issue
573 Practical solutions to kconfig recursive issue
576 Developers who run into the recursive Kconfig issue have two options
596 Below is a list of examples of prior fixes for these types of recursive issues;
637 the current known recursive dependency issues. It is not known if this would
[all …]
/Linux-v5.4/scripts/gdb/linux/
Ddevice.py90 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-v5.4/tools/perf/util/
Ddwarf-aux.c656 bool recursive; member
678 if (!lw->recursive) in __die_walk_funclines_cb()
696 static int __die_walk_funclines(Dwarf_Die *sp_die, bool recursive, in __die_walk_funclines() argument
700 .recursive = recursive, in __die_walk_funclines()
/Linux-v5.4/Documentation/admin-guide/sysctl/
Duser.rst33 This recursive counting of created objects ensures that creating a
/Linux-v5.4/security/tomoyo/
Dutil.c844 goto recursive; in tomoyo_path_matches_pattern2()
860 recursive: in tomoyo_path_matches_pattern2()
/Linux-v5.4/Documentation/filesystems/
Dceph.txt56 Ceph also provides some recursive accounting on directories for nested
61 no 'du' or similar recursive scan of the file system is required.
Dpath-lookup.txt60 name in the name string, and require some recursive path walking. Mount points
/Linux-v5.4/include/sound/
Dhda_codec.h349 hda_nid_t nid, int recursive);
/Linux-v5.4/Documentation/
Dpi-futex.txt18 recursive locking, etc.
Dkprobes.txt129 For example, if the function is non-recursive and is called with a
131 non-recursive and can never relinquish the CPU (e.g., via a semaphore
298 (trapping) such functions can cause a recursive trap (e.g. double
/Linux-v5.4/sound/pci/hda/
Dhda_codec.c265 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-v5.4/Documentation/ia64/
Dmca.rst85 own stack as running on that cpu. Then a recursive error gets a
/Linux-v5.4/Documentation/admin-guide/cgroup-v1/
Dblkio-controller.rst242 same information as their non-recursive counterparts but
/Linux-v5.4/Documentation/core-api/
Dprintk-formats.rst388 Implements a "recursive vsnprintf".
Dassoc_array.rst495 slot in that parent that points to it. None-recursive iteration uses these to
/Linux-v5.4/lib/
DKconfig438 modify. The algorithms are non-recursive, and the trees are highly
/Linux-v5.4/Documentation/admin-guide/device-mapper/
Dthin-provisioning.rst17 recursive snapshots (snapshots of snapshots of snapshots ...). The
/Linux-v5.4/Documentation/driver-api/rapidio/
Drapidio.rst254 The enumeration process traverses the network using a recursive depth-first
/Linux-v5.4/Documentation/filesystems/caching/
Dfscache.txt109 recursive, stack space is limited, and indices can only be children of
/Linux-v5.4/Documentation/RCU/
DwhatisRCU.txt579 one read-side critical section to another. It also assumes recursive
580 reader-writer locks: If you try this with non-recursive locks, and
/Linux-v5.4/fs/
Dnamespace.c2320 static struct file *open_detached_copy(struct path *path, bool recursive) in open_detached_copy() argument
2331 mnt = __do_loopback(path, recursive); in open_detached_copy()
/Linux-v5.4/Documentation/kernel-hacking/
Dlocking.rst124 Neither type of lock is recursive: see
885 (spinlocks, rwlocks and mutexes are not recursive in Linux). This is

12