/linux-4.4.14/net/appletalk/ |
D | aarp.c | 77 static struct aarp_entry *resolved[AARP_HASH_SIZE]; variable 320 __aarp_expire_timer(&resolved[ct]); in aarp_expire_timeout() 346 __aarp_expire_device(&resolved[ct], dev); in aarp_device_event() 375 __aarp_expire_all(&resolved[ct]); in aarp_purge() 619 a = __aarp_find_entry(resolved[hash], dev, sa); in aarp_send_ddp() 702 a->next = resolved[hash]; in __aarp_resolved() 703 resolved[hash] = a; in __aarp_resolved() 835 a = __aarp_find_entry(resolved[sa.s_node % in aarp_rcv() 901 __aarp_expire_device(&resolved[ct], dev); in aarp_device_down() 940 if (table == resolved) { in iter_next() [all …]
|
/linux-4.4.14/net/ceph/ |
D | Kconfig | 38 be resolved using the CONFIG_DNS_RESOLVER facility.
|
/linux-4.4.14/fs/hostfs/ |
D | hostfs_kern.c | 143 char *name, *resolved, *end; in follow_link() local 169 resolved = kmalloc(len, GFP_KERNEL); in follow_link() 170 if (resolved == NULL) { in follow_link() 175 sprintf(resolved, "%s%s", link, name); in follow_link() 178 return resolved; in follow_link()
|
/linux-4.4.14/Documentation/ABI/testing/ |
D | sysfs-firmware-ofw | 25 directory name is the resolved path component name (node
|
/linux-4.4.14/Documentation/power/ |
D | drivers-testing.txt | 22 Once you have resolved the suspend/resume-related problems with your test system
|
/linux-4.4.14/Documentation/locking/ |
D | lglock.txt | 63 On -RT this deadlock scenario is resolved by the arch_spin_locks in the 138 The deadlock noted for non-RT above is resolved due to rt_mutexes
|
/linux-4.4.14/Documentation/vm/ |
D | userfaultfd.txt | 14 Userfaults are delivered and resolved through the userfaultfd syscall. 119 userfault was already resolved and waken by a UFFDIO_COPY|ZEROPAGE run
|
D | unevictable-lru.txt | 259 Nick resolved this by putting mlocked pages back on the lru list before
|
/linux-4.4.14/Documentation/devicetree/ |
D | overlay-notes.txt | 39 The overlay bar.dts, when loaded (and resolved as described in [2]) should
|
/linux-4.4.14/Documentation/development-process/ |
D | 6.Followthrough | 89 anywhere? Most technical disagreements can be resolved through discussion, 103 most of the review issues have been resolved, the next step is usually 131 Now they can be resolved at leisure, before the merge window opens.
|
D | 7.AdvancedTopics | 107 useful in such situations; it remembers how merge conflicts were resolved
|
/linux-4.4.14/Documentation/i2c/busses/ |
D | i2c-ali15x3 | 105 the SMBus will hang and this can only be resolved by
|
/linux-4.4.14/Documentation/filesystems/nfs/ |
D | pnfs.txt | 29 lsegs reference device ids, which are resolved per nfs_client and
|
/linux-4.4.14/Documentation/filesystems/ |
D | path-lookup.txt | 6 will be resolved. Paths are resolved by walking the namespace tree, starting 363 condition that can't be resolved in rcu-walk mode. Ideally, we drop rcu-walk
|
D | romfs.txt | 172 from the filesystem. It might be resolved by reordering file data to
|
D | spufs.txt | 475 ENOENT Part of pathname could not be resolved.
|
/linux-4.4.14/Documentation/networking/ |
D | netdev-features.txt | 73 All dependencies between features should be resolved here. The resulting
|
D | switchdev.txt | 366 nexthop gateways must be resolved to the neighbor's mac address. Neighbor mac 373 NETEVENT_NEIGH_UPDATE. The device can be programmed with resolved nexthops
|
D | e1000.txt | 272 not be resolved by the use of the TxDescriptorStep parameter. As the
|
D | ip-sysctl.txt | 1132 receiving answer from the resolved target while decreasing
|
/linux-4.4.14/ |
D | REPORTING-BUGS | 116 resolved (see Documentation/oops-tracing.txt)
|
/linux-4.4.14/Documentation/ |
D | printk-formats.txt | 55 actually function descriptors which must first be resolved. The 'F' and
|
D | sysfs-rules.txt | 52 pointing to /sys/devices must always be resolved to their real
|
D | devices.txt | 3325 installed in the order the symlinks are resolved.
|
/linux-4.4.14/fs/affs/ |
D | Changes | 208 now resolved only once in lookup(). The backside
|
/linux-4.4.14/tools/perf/Documentation/ |
D | perf-report.txt | 65 Only display entries resolved to a symbol.
|
/linux-4.4.14/drivers/net/ethernet/rocker/ |
D | rocker.c | 3083 bool resolved = true; in rocker_port_ipv4_nh() local 3105 resolved = false; in rocker_port_ipv4_nh() 3110 resolved = !is_zero_ether_addr(found->eth_dst); in rocker_port_ipv4_nh() 3125 if (!resolved) in rocker_port_ipv4_nh()
|
/linux-4.4.14/drivers/net/usb/ |
D | Kconfig | 369 # are ever resolved ... then remove "experimental"
|
/linux-4.4.14/Documentation/kbuild/ |
D | kconfig-language.txt | 437 historical issues resolved through these different solutions.
|
/linux-4.4.14/Documentation/nvdimm/ |
D | nvdimm.txt | 427 devices with the resolved/exclusive DPA-boundaries for the nd_pmem or
|
/linux-4.4.14/lib/ |
D | Kconfig.debug | 750 where a lockup must be resolved ASAP. 804 where a hung tasks must be resolved ASAP.
|
/linux-4.4.14/Documentation/cdrom/ |
D | cdrom-standard.tex | 532 in audio frames. Once these issues are resolved, this code should be
|
/linux-4.4.14/drivers/scsi/aic7xxx/ |
D | aic7xxx.seq | 57 * a later time. This problem cannot be resolved by holding a single entry
|
/linux-4.4.14/Documentation/block/ |
D | biodoc.txt | 836 This is to be resolved. The eventual direction is to replace kiobuf
|
/linux-4.4.14/Documentation/virtual/kvm/ |
D | api.txt | 3213 resolved by the kernel.
|