| /Linux-v5.4/kernel/locking/ |
| D | test-ww_mutex.c | 153 bool resolve; member
170 if (abba->resolve && err == -EDEADLK) { in test_abba_work()
184 static int test_abba(bool resolve) in test_abba() argument
195 abba.resolve = resolve; in test_abba()
206 if (resolve && err == -EDEADLK) { in test_abba()
221 if (resolve) { in test_abba()
|
| /Linux-v5.4/tools/perf/Documentation/ |
| D | jit-interface.txt | 1 perf supports a simple JIT interface to resolve symbols for dynamic code generated
|
| /Linux-v5.4/net/atm/ |
| D | lec.h | 46 int (*resolve) (struct net_device *dev, const u8 *dst_mac, int force, member
|
| /Linux-v5.4/drivers/net/phy/ |
| D | phylink.c | 69 struct work_struct resolve; member
473 struct phylink *pl = container_of(w, struct phylink, resolve); in phylink_resolve()
533 queue_work(system_power_efficient_wq, &pl->resolve); in phylink_resolve()
541 queue_work(system_power_efficient_wq, &pl->resolve); in phylink_run_resolve()
550 queue_work(system_power_efficient_wq, &pl->resolve); in phylink_run_resolve_and_disable()
551 flush_work(&pl->resolve); in phylink_run_resolve_and_disable()
622 INIT_WORK(&pl->resolve, phylink_resolve); in phylink_create()
693 cancel_work_sync(&pl->resolve); in phylink_destroy()
903 flush_work(&pl->resolve); in phylink_disconnect_phy()
|
| /Linux-v5.4/Documentation/media/uapi/v4l/ |
| D | pixfmt-cnf4.rst | 16 unable to resolve any signal and 15 indicating maximum level of confidence for
|
| /Linux-v5.4/tools/lib/traceevent/Documentation/ |
| D | libtraceevent-func_apis.txt | 27 Some tools may have already a way to resolve the kernel functions. These APIs
40 _tep_find_function_address()_, and _tep_print_func_field()_ to resolve
127 /* These APIs use my_resolve_kernel_addr() to resolve the addr */
|
| /Linux-v5.4/Documentation/devicetree/ |
| D | dynamic-resolution-notes.txt | 17 2. Adjust all the local phandles of the tree to resolve by that amount.
|
| /Linux-v5.4/Documentation/maintainer/ |
| D | rebasing-and-merging.rst | 165 maintainer merges with the upstream in order to resolve merge conflicts
179 how you would resolve things. Mention that branch in your pull request,
188 resolve dependencies. These dependency issues do happen at times, and
189 sometimes a cross-merge with another tree is the best way to resolve them;
195 needed. Merging another subsystem tree to resolve a dependency risks
|
| /Linux-v5.4/kernel/bpf/ |
| D | btf.c | 283 int (*resolve)(struct btf_verifier_env *env, member
1482 .resolve = btf_df_resolve,
1785 .resolve = btf_modifier_resolve,
1794 .resolve = btf_ptr_resolve,
1835 .resolve = btf_df_resolve,
2024 .resolve = btf_array_resolve,
2289 .resolve = btf_struct_resolve,
2445 .resolve = btf_df_resolve,
2523 .resolve = btf_df_resolve,
2566 .resolve = btf_df_resolve,
[all …]
|
| /Linux-v5.4/Documentation/kbuild/ |
| D | Kconfig.recursion-issue-01 | 40 # so trivial to resolve, we provide another example below of practical
|
| D | kbuild.rst | 12 is used by modprobe to deterministically resolve aliases that match
|
| D | kconfig-macro-language.rst | 46 Then, Kconfig moves onto the evaluation stage to resolve inter-symbol
|
| /Linux-v5.4/Documentation/power/ |
| D | drivers-testing.rst | 20 resolve all suspend/resume-related problems in the test system before you start
|
| /Linux-v5.4/Documentation/admin-guide/mm/ |
| D | userfaultfd.rst | 30 resolve the userfaults it receives via 1) or to manage the virtual
91 uffdio_register.ioctls bitmask of ioctls that are suitable to resolve
103 The primary ioctl to resolve userfaults is UFFDIO_COPY. That
|
| /Linux-v5.4/Documentation/networking/device_drivers/intel/ |
| D | ixgb.rst | 389 cable assembly may resolve the issue.
395 (1 m or shorter). If this situation occurs, using a longer cable may resolve
401 this situation occurs, using a different cable assembly may resolve the issue.
453 "ethtool -K eth0 tso off" may resolve the problem.
|
| /Linux-v5.4/Documentation/livepatch/ |
| D | module-elf-format.rst | 48 since the kernel module loader cannot resolve them and will therefore
53 module Elf output. Using these dynrela sections, livepatch could resolve
245 that the module loader can identify them and not attempt to resolve them.
|
| /Linux-v5.4/drivers/net/wireless/intel/iwlegacy/ |
| D | Kconfig | 90 as the debug information can assist others in helping you resolve
|
| /Linux-v5.4/drivers/net/wireless/intel/iwlwifi/ |
| D | Kconfig | 118 as the debug information can assist others in helping you resolve
|
| /Linux-v5.4/Documentation/process/ |
| D | kernel-enforcement-statement.rst | 46 failed to resolve the problem.
|
| /Linux-v5.4/Documentation/filesystems/nfs/ |
| D | nfs.txt | 82 - the hostname to resolve
|
| /Linux-v5.4/drivers/gpu/drm/i915/ |
| D | Kconfig.debug | 144 performance but will help resolve GuC related issues.
|
| /Linux-v5.4/Documentation/admin-guide/sysctl/ |
| D | net.rst | 371 aarp-resolve-time
374 The amount of time we will spend trying to resolve an Appletalk address.
|
| /Linux-v5.4/Documentation/RCU/ |
| D | torture.txt | 74 to resolve RCU priority inversion.
|
| /Linux-v5.4/Documentation/hid/ |
| D | hiddev.rst | 242 same usage code, this mode serves to resolve such
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | sysfs-class-net | 175 used to resolve interfaces chaining, linking and stacking.
|
