| /Linux-v6.6/net/appletalk/ |
| D | aarp.c | 71 static struct aarp_entry *resolved[AARP_HASH_SIZE]; variable
314 __aarp_expire_timer(&resolved[ct]); in aarp_expire_timeout()
340 __aarp_expire_device(&resolved[ct], dev); in aarp_device_event()
369 __aarp_expire_all(&resolved[ct]); in aarp_purge()
613 a = __aarp_find_entry(resolved[hash], dev, sa); in aarp_send_ddp()
696 a->next = resolved[hash]; in __aarp_resolved()
697 resolved[hash] = a; in __aarp_resolved()
829 a = __aarp_find_entry(resolved[sa.s_node % in aarp_rcv()
904 __aarp_expire_device(&resolved[ct], dev); in aarp_device_down()
938 if (table == resolved) { in iter_next()
[all …]
|
| /Linux-v6.6/Documentation/ABI/testing/ |
| D | sysfs-bus-event_source-devices-hv_gpci | 99 HCALL with return error type "H_AUTHORITY" can be resolved during
131 HCALL with return error type "H_AUTHORITY" can be resolved during
163 HCALL with return error type "H_AUTHORITY" can be resolved during
195 HCALL with return error type "H_AUTHORITY" can be resolved during
227 HCALL with return error type "H_AUTHORITY" can be resolved during
|
| D | sysfs-firmware-ofw | 25 directory name is the resolved path component name (node
|
| /Linux-v6.6/drivers/acpi/acpica/ |
| D | dspkginit.c | 396 if (element->reference.resolved) { in acpi_ds_resolve_package_element()
473 element->reference.resolved = TRUE; in acpi_ds_resolve_package_element()
|
| D | dsobject.c | 115 obj_desc->reference.resolved = TRUE; in acpi_ds_build_internal_object()
126 obj_desc->reference.resolved = FALSE; in acpi_ds_build_internal_object()
|
| D | acobject.h | 312 u8 resolved; /* Reference has been resolved to a value */ member
|
| /Linux-v6.6/tools/net/ynl/lib/ |
| D | nlspec.py | 412 resolved = []
424 resolved.append(elem)
426 if len(resolved) == 0:
|
| /Linux-v6.6/net/ceph/ |
| D | Kconfig | 42 be resolved using the CONFIG_DNS_RESOLVER facility.
|
| /Linux-v6.6/arch/arm/boot/dts/ti/omap/ |
| D | am57xx-evm.dtso | 22 // resolved here correcly based on
|
| /Linux-v6.6/Documentation/livepatch/ |
| D | module-elf-format.rst | 104 livepatch symbol. These must be resolved before livepatch can call
192 objects, whose addresses cannot be resolved by the module loader (because
199 symbols are resolved simply when the target module loads. In any case, for
201 section must be resolved before livepatch can call apply_relocate_add() for
|
| /Linux-v6.6/fs/hostfs/ |
| D | hostfs_kern.c | 146 char *name, *resolved, *end; in follow_link() local
172 resolved = kasprintf(GFP_KERNEL, "%s%s", link, name); in follow_link()
173 if (resolved == NULL) { in follow_link()
179 return resolved; in follow_link()
|
| /Linux-v6.6/drivers/gpu/drm/amd/display/ |
| D | Kconfig | 21 has been resolved: https://github.com/llvm/llvm-project/issues/41896.
|
| /Linux-v6.6/Documentation/translations/zh_CN/maintainer/ |
| D | pull-requests.rst | 100 all been resolved (apologies to anyone living near Canberra for the
|
| /Linux-v6.6/Documentation/power/ |
| D | drivers-testing.rst | 27 Once you have resolved the suspend/resume-related problems with your test system
|
| /Linux-v6.6/tools/perf/Documentation/ |
| D | perf-mem.txt | 65 Only display entries resolved to a symbol.
|
| /Linux-v6.6/Documentation/filesystems/nfs/ |
| D | pnfs.rst | 32 lsegs reference device ids, which are resolved per nfs_client and
|
| /Linux-v6.6/Documentation/hwmon/ |
| D | peci-cputemp.rst | 86 temp[6-N]_label Provides string "Core X", where X is resolved core
|
| /Linux-v6.6/Documentation/userspace-api/ |
| D | iommufd.rst | 208 There are still a few gaps to be resolved to catch up with VFIO type1, as
223 - PRI support with faults resolved in userspace
|
| /Linux-v6.6/Documentation/filesystems/spufs/ |
| D | spu_create.rst | 83 ENOENT Part of pathname could not be resolved.
|
| /Linux-v6.6/Documentation/networking/devlink/ |
| D | devlink-dpipe.rst | 156 interactions between tables can be resolved.
236 In case the egress RIF and destination MAC have been resolved by previous
|
| /Linux-v6.6/Documentation/process/ |
| D | 6.Followthrough.rst | 100 anywhere? Most technical disagreements can be resolved through discussion,
115 most of the review issues have been resolved, the next step is usually
143 Now they can be resolved at leisure, before the merge window opens.
|
| D | kernel-enforcement-statement.rst | 48 Finally, once a non-compliance issue is resolved, we hope the user will feel
|
| /Linux-v6.6/Documentation/i2c/busses/ |
| D | i2c-ali15x3.rst | 116 the SMBus will hang and this can only be resolved by
|
| /Linux-v6.6/Documentation/bpf/ |
| D | llvm_reloc.rst | 120 data bitsize is 32 (4 bytes). The relocation can be resolved with
127 bitsize is 64 (8 bytes). The relocation can be resolved with
133 is involved, ``R_BPF_64_NODYLD32`` types of relocations should not be resolved
|
| /Linux-v6.6/Documentation/devicetree/ |
| D | overlay-notes.rst | 56 when loaded (and resolved as described in [1]) should result in foo+bar.dts::
|
