| /linux-4.1.27/fs/exportfs/ |
| D | expfs.c | 42 int (*acceptable)(void *context, struct dentry *dentry), in find_acceptable_alias()
48 if (acceptable(context, result)) in find_acceptable_alias()
58 if (dentry != result && acceptable(context, dentry)) { in find_acceptable_alias()
414 int (*acceptable)(void *, struct dentry *), void *context) in exportfs_decode_fh()
447 if (!acceptable(context, result)) { in exportfs_decode_fh()
468 alias = find_acceptable_alias(result, acceptable, context); in exportfs_decode_fh()
529 alias = find_acceptable_alias(result, acceptable, context); in exportfs_decode_fh()
|
| /linux-4.1.27/drivers/pci/pcie/ |
| D | aspm.c | 68 struct aspm_latency acceptable[8]; member
308 struct aspm_latency *acceptable; in pcie_aspm_check_latency() local
317 acceptable = &link->acceptable[PCI_FUNC(endpoint->devfn)]; in pcie_aspm_check_latency()
322 (link->latency_up.l0s > acceptable->l0s)) in pcie_aspm_check_latency()
327 (link->latency_dw.l0s > acceptable->l0s)) in pcie_aspm_check_latency()
336 (latency + l1_switch_latency > acceptable->l1)) in pcie_aspm_check_latency()
408 struct aspm_latency *acceptable = in pcie_aspm_cap_init() local
409 &link->acceptable[PCI_FUNC(child->devfn)]; in pcie_aspm_cap_init()
418 acceptable->l0s = calc_l0s_acceptable(encoding); in pcie_aspm_cap_init()
421 acceptable->l1 = calc_l1_acceptable(encoding); in pcie_aspm_cap_init()
|
| /linux-4.1.27/include/linux/ |
| D | exportfs.h | 224 int fh_len, int fileid_type, int (*acceptable)(void *, struct dentry *),
|
| /linux-4.1.27/Documentation/ |
| D | CodeOfConflict | 16 uncomfortable due to this process, that is not acceptable. If so,
|
| D | pnp.txt | 64 Dependent: 01 - Priority acceptable
69 Dependent: 02 - Priority acceptable
|
| D | HOWTO | 285 documents what kinds of changes are acceptable for the -stable tree, and
449 Remember, being wrong is acceptable as long as you are willing to work
554 Also realize that it is not acceptable to send patches for inclusion
|
| D | kernel-per-CPU-kthreads.txt | 273 timer down to a level that is acceptable for your workload.
|
| D | bcache.txt | 241 maximum acceptable sequential size for any single request.
|
| D | dma-buf-sharing.txt | 402 always a slower path, so some inefficiencies should be acceptable.
|
| D | SubmittingPatches | 551 acceptable according to the Reviewer's Statement:
|
| D | memory-barriers.txt | 1929 The following sequence of events is acceptable:
|
| /linux-4.1.27/Documentation/networking/ |
| D | dccp.txt | 114 range 0..15 are acceptable. The default setting is 0 (full coverage),
117 sets a threshold, where again values 0..15 are acceptable. The default
120 coverage value are also acceptable. The higher the number, the more
|
| D | tproxy.txt | 50 acceptable in certain situations. (Think of proxying UDP for example: you won't
|
| D | nf_conntrack-sysctl.txt | 131 received an (acceptable) ACK from the destination. If this number
|
| D | cs89x0.txt | 157 installing a CS8900-based adapter and the default configuration is acceptable.)
|
| /linux-4.1.27/Documentation/power/regulator/ |
| D | consumer.txt | 79 Where min_uV and max_uV are the minimum and maximum acceptable voltages in
109 Where min_uA and max_uA are the minimum and maximum acceptable current limit in
|
| /linux-4.1.27/Documentation/scsi/ |
| D | megaraid.txt | 31 "Shared code in a third module, a "library module", is an acceptable
|
| D | ChangeLog.megaraid | 563 "Shared code in a third module, a "library module", is an acceptable
|
| D | scsi_mid_low_api.txt | 1182 "proc_name" should only contain characters acceptable
|
| /linux-4.1.27/Documentation/timers/ |
| D | timers-howto.txt | 91 be balanced with what is an acceptable upper bound on
|
| /linux-4.1.27/Documentation/devicetree/bindings/reserved-memory/ |
| D | reserved-memory.txt | 42 acceptable to allocate from.
|
| /linux-4.1.27/Documentation/hwmon/ |
| D | submitting-patches | 75 and messages printed after a successful detection are acceptable, but it
|
| D | pc87360 | 84 RPM as the lowest acceptable accuracy.
|
| D | sysfs-interface | 731 checked if its acceptable. Be careful with further conversions on the value
|
| /linux-4.1.27/Documentation/sound/oss/ |
| D | SoundPro | 52 The IRQ and DMA values can be any that are considered acceptable for a
|
| /linux-4.1.27/Documentation/arm/ |
| D | IXP4xx | 90 cases the performance hit is acceptable. In addition, you cannot
|
| /linux-4.1.27/Documentation/arm/nwfpe/ |
| D | README.FPE | 89 equivalent to the MUF/DVF/RDV instructions. This is acceptable according
|
| /linux-4.1.27/arch/arm/nwfpe/ |
| D | softfloat-specialize | 24 Derivative works are acceptable, even for commercial purposes, so long as
|
| D | softfloat-macros | 24 Derivative works are acceptable, even for commercial purposes, so long as
|
| /linux-4.1.27/arch/arm/mach-ixp4xx/ |
| D | Kconfig | 218 acceptable. In addition, you cannot mmap() PCI devices in this
|
| /linux-4.1.27/arch/m68k/ifpsp060/ |
| D | TEST.DOC | 167 is acceptable.
|
| /linux-4.1.27/Documentation/fb/ |
| D | modedb.txt | 107 - acceptable refresh rates are 50, 60, 70 or 85 Hz only
|
| /linux-4.1.27/Documentation/filesystems/nfs/ |
| D | nfs-rdma.txt | 49 Any device supported by the drivers in drivers/infiniband/hw is acceptable.
|
| /linux-4.1.27/Documentation/prctl/ |
| D | seccomp_filter.txt | 55 acceptable values to inform the kernel which action should be
|
| /linux-4.1.27/Documentation/vm/ |
| D | slub.txt | 123 into one slab in order for the allocation order to be acceptable.
|
| /linux-4.1.27/Documentation/filesystems/ |
| D | sysfs.txt | 60 value per file, so it is socially acceptable to express an array of
|
| D | proc.txt | 1464 be used to tune the badness score. Its acceptable values range from -16
|
| /linux-4.1.27/Documentation/development-process/ |
| D | 3.Early-stage | 83 acceptable for mainline merging. It is better to find out about
|
| D | 6.Followthrough | 192 acceptable to you. There is a certain resistance to merging patches which
|
| /linux-4.1.27/net/ipv4/ |
| D | tcp_input.c | 5704 bool acceptable; in tcp_rcv_state_process() local
5776 acceptable = tcp_ack(sk, skb, FLAG_SLOWPATH | in tcp_rcv_state_process()
5781 if (!acceptable) in tcp_rcv_state_process()
5858 if (!acceptable) in tcp_rcv_state_process()
|
| /linux-4.1.27/Documentation/block/ |
| D | cfq-iosched.txt | 37 throughput and acceptable latencies.
|
| /linux-4.1.27/arch/x86/math-emu/ |
| D | README | 147 acceptable (and work) in real mode. A small test program developed to
|
| /linux-4.1.27/Documentation/RCU/ |
| D | checklist.txt | 321 Similarly, disabling preemption is not an acceptable substitute
|
| /linux-4.1.27/Documentation/cgroups/ |
| D | unified-hierarchy.txt | 375 gives acceptable performance is found.
|
| D | cpusets.txt | 577 and whether it is acceptable or not depends on your situation.
|
| /linux-4.1.27/Documentation/powerpc/ |
| D | hvcs.txt | 217 passed through them are NOT acceptable for providing interactive console
|
| /linux-4.1.27/Documentation/sysctl/ |
| D | vm.txt | 115 acceptable trade for large contiguous free memory. Set to 0 to prevent
|
| /linux-4.1.27/Documentation/filesystems/caching/ |
| D | netfs-api.txt | 346 acceptable to pass this token back to this function as the parent to another
|
| /linux-4.1.27/Documentation/security/ |
| D | Smack.txt | 413 Access mode specifications can be in any order. Examples of acceptable rules
|
| /linux-4.1.27/scripts/genksyms/ |
| D | lex.lex.c_shipped | 1918 * more volatile, which is acceptable. Also, such collisions are quite rare,
|
| /linux-4.1.27/Documentation/m68k/ |
| D | kernel-options.txt | 802 period. Default is 500; acceptable values are 250 - 1000.
|
| /linux-4.1.27/ |
| D | MAINTAINERS | 95 One pattern per line. Multiple F: lines acceptable.
98 One pattern per line. Multiple N: lines acceptable.
117 One regex pattern per line. Multiple K: lines acceptable.
|
| /linux-4.1.27/Documentation/virtual/uml/ |
| D | UserModeLinux-HOWTO.txt | 1638 isn't acceptable for some reason. The rest of the arguments describe
|