| /linux-4.4.14/arch/mips/kvm/ |
| D | 00README.txt | 21 This will be implemented in a future release.
27 This will be fixed in a future release.
31 This will be fixed in a future release
|
| /linux-4.4.14/Documentation/x86/x86_64/ |
| D | cpu-hotplug-spec | 13 For CPU hotplug Linux/x86-64 expects now that any possible future hotpluggable
16 of disabled LAPICs to compute the maximum number of future CPUs.
|
| D | boot-options.txt | 269 in the future.
|
| /linux-4.4.14/arch/arm/crypto/ |
| D | sha256-core.S_shipped | 163 ldr r2,[sp,#2*4] @ from future BODY_16_xx
165 ldr r1,[sp,#15*4] @ from future BODY_16_xx
221 ldr r2,[sp,#3*4] @ from future BODY_16_xx
223 ldr r1,[sp,#0*4] @ from future BODY_16_xx
279 ldr r2,[sp,#4*4] @ from future BODY_16_xx
281 ldr r1,[sp,#1*4] @ from future BODY_16_xx
337 ldr r2,[sp,#5*4] @ from future BODY_16_xx
339 ldr r1,[sp,#2*4] @ from future BODY_16_xx
395 ldr r2,[sp,#6*4] @ from future BODY_16_xx
397 ldr r1,[sp,#3*4] @ from future BODY_16_xx
[all …]
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | cramfs.txt | 45 mind the filesystem becoming unreadable to future kernels.
54 >12 ulelong x future 0x%x
64 >524 ulelong x future 0x%x
|
| D | fiemap.txt | 42 fiemap interface to grow in the future but without losing
105 a general property does not have to know all existing and future flags
113 worry about all present and future flags which might imply unaligned
|
| D | overlayfs.txt | 158 filesystem - future operations on the file are barely noticed by the
200 fixed in the future.
204 be addressed in the future.
|
| D | squashfs.txt | 253 read in the near future. Temporarily caching them ensures they are available
254 for near future access without requiring an additional read and decompress.
256 In the future this internal cache may be replaced with an implementation which
|
| D | gfs2-uevents.txt | 84 lock_nolock or lock_dlm. In the future other lock managers
|
| D | romfs.txt | 133 special files, they may have other uses in the future. Additionally,
|
| D | logfs.txt | 13 for future purposes, making a total of 4096 Bytes.
|
| D | ntfs.txt | 108 nls=name in the future. See description for nls=name.
120 nls=utf8 but please use nls=utf8 in the future and
|
| D | ext4.txt | 106 2.2 Candidate features for future inclusion
596 behaviour may change in the future as it is
|
| /linux-4.4.14/drivers/staging/rts5208/ |
| D | TODO | 5 rts5208/5288 in the future
|
| /linux-4.4.14/Documentation/arm64/ |
| D | booting.txt | 142 x1 = 0 (reserved for future use)
143 x2 = 0 (reserved for future use)
144 x3 = 0 (reserved for future use)
240 x0 = 0 (reserved for future use)
241 x1 = 0 (reserved for future use)
242 x2 = 0 (reserved for future use)
243 x3 = 0 (reserved for future use)
|
| D | acpi_object_usage.txt | 158 x86 only table as of ACPI 5.1; future versions have been adapted for
509 still be useful into the future. C-states and P-states will still be
549 While this may change in the future, there are several classes of objects
580 implemented though that may change in the future.
|
| /linux-4.4.14/Documentation/security/ |
| D | tomoyo.txt | 45 --- What is future plan? ---
52 We hope that LSM becomes stackable in future. Meanwhile, you can use non-LSM
|
| D | keys-trusted-encrypted.txt | 15 (future) PCR values, so keys are easily migrated to new pcr values, such as
|
| /linux-4.4.14/include/uapi/linux/ |
| D | cramfs_fs.h | 58 __u32 future; /* reserved for future use */ member
|
| /linux-4.4.14/Documentation/hwmon/ |
| D | ab8500 | 22 in future.
|
| D | k8temp | 36 1 degree C. It is expected that future CPU will have better resolution. The
|
| /linux-4.4.14/Documentation/ABI/stable/ |
| D | sysfs-firmware-opal-elog | 33 user space to solve the problem. In future, we may
47 In the future there may be additional types.
|
| D | sysfs-module | 13 by design and may be removed in the future.
|
| D | sysfs-class-ubi | 17 However, if in the future UBI needs on-flash format changes
20 future backward-compatible (but forward-incompatible)
|
| /linux-4.4.14/Documentation/virtual/kvm/ |
| D | nested-vmx.txt | 97 u32 padding[7]; /* room for future expansion */
120 u64 padding64[8]; /* room for future expansion */
163 natural_width paddingl[8]; /* room for future expansion */
210 u32 padding32[8]; /* room for future expansion */
|
| D | cpuid.txt | 19 and will be updated if more functions are added in the future.
|
| D | msr.txt | 134 future. Its usage is deprecated.
144 future. Its usage is deprecated.
229 changes in this structure in the future.
|
| D | hypercalls.txt | 83 is used in the hypercall for future use.
|
| D | mmu.txt | 240 to avoid emulation in the future.
319 guest will use it in the near future
|
| /linux-4.4.14/sound/mips/ |
| D | Kconfig | 36 this driver as it will be removed in the future.
|
| /linux-4.4.14/arch/parisc/math-emu/ |
| D | README | 4 someone in the future, with access to HP-UX source code, is generous
|
| /linux-4.4.14/Documentation/devicetree/bindings/clock/ti/ |
| D | fapll.txt | 3 Binding status: Unstable - ABI compatibility may be broken in the future
|
| D | clockdomain.txt | 3 Binding status: Unstable - ABI compatibility may be broken in the future
|
| D | autoidle.txt | 3 Binding status: Unstable - ABI compatibility may be broken in the future
|
| D | fixed-factor-clock.txt | 3 Binding status: Unstable - ABI compatibility may be broken in the future
|
| D | composite.txt | 3 Binding status: Unstable - ABI compatibility may be broken in the future
|
| D | apll.txt | 3 Binding status: Unstable - ABI compatibility may be broken in the future
|
| D | interface.txt | 3 Binding status: Unstable - ABI compatibility may be broken in the future
|
| D | mux.txt | 3 Binding status: Unstable - ABI compatibility may be broken in the future
|
| D | gate.txt | 3 Binding status: Unstable - ABI compatibility may be broken in the future
|
| D | dpll.txt | 3 Binding status: Unstable - ABI compatibility may be broken in the future
|
| D | divider.txt | 3 Binding status: Unstable - ABI compatibility may be broken in the future
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/samsung/ |
| D | exynos-adc.txt | 8 and future SoCs from Samsung
16 future controllers.
|
| /linux-4.4.14/Documentation/devicetree/bindings/display/armada/ |
| D | marvell,dove-lcd.txt | 19 Further clocks may be added in the future according to requirements of
|
| /linux-4.4.14/Documentation/devicetree/bindings/clock/ |
| D | keystone-gate.txt | 1 Status: Unstable - ABI compatibility may be broken in the future
|
| D | keystone-pll.txt | 1 Status: Unstable - ABI compatibility may be broken in the future
|
| /linux-4.4.14/Documentation/wimax/ |
| D | README.wimax | 12 services to current and future WiMAX devices from any vendor.
17 accommodate future requirements.
|
| D | README.i2400m | 84 services to current and future WiMAX devices from any vendor; please
|
| /linux-4.4.14/Documentation/devicetree/bindings/display/msm/ |
| D | gpu.txt | 13 - qcom,chipid: gpu chip-id. Note this may become optional for future
|
| /linux-4.4.14/arch/x86/boot/ |
| D | pmjump.S | 65 # Clear registers to allow for future extensions to the
|
| /linux-4.4.14/Documentation/devicetree/bindings/interrupt-controller/ |
| D | arm,gic-v3.txt | 16 interrupts. Other values are reserved for future use.
27 Cells 4 and beyond are reserved for future use. When the 1st cell
|
| /linux-4.4.14/Documentation/powerpc/ |
| D | cxl.txt | 217 For ABI padding and future extensions
294 For future extensions and padding.
313 For future extensions and padding.
343 For future extensions
363 For future extensions and padding
|
| D | firmware-assisted-dump.txt | 256 additional fields (in future) to this structure without affecting
260 whenever a new field is added to the structure in future. The version
265 for future field additions.
|
| D | transactional_memory.txt | 107 delivered. For future compatibility the MSR.TS field should be checked to
|
| D | eeh-pci-error-recovery.txt | 296 which may be addressed in future revisions. But first, note that the
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | sysfs-firmware-ofw | 17 in the future, but the symlink is the stable ABI.
|
| D | dev-kmsg | 106 should be the same. In the future, the in-kernel concatenation
|
| D | sysfs-bus-pci | 73 MSI-X for any future drivers of the device. If the device
74 is a bridge, MSI and MSI-X will be disallowed for future
|
| /linux-4.4.14/Documentation/cpu-freq/ |
| D | boost.txt | 85 This functionality is considered legacy and will be removed in some future
93 does not support it, but this may be implemented in the future.
|
| D | governors.txt | 52 addition in the near future, but likely many more as there are various
|
| /linux-4.4.14/arch/alpha/lib/ |
| D | ev6-memset.S | 161 subq $3, 24, $2 # E : For determining future wh64 addresses
338 subq $3, 24, $2 # E : For determining future wh64 addresses
525 subq $3, 24, $2 # E : For determining future wh64 addresses
|
| /linux-4.4.14/include/linux/ |
| D | ti_wilink_st.h | 310 u8 future[24]; member
|
| /linux-4.4.14/Documentation/isdn/ |
| D | README.pcbit | 31 allow normal operation. Plans for the future include cooperation with
|
| D | README.concap | 14 interface, please let me know. I'm willing to include them in future
74 better in future.
|
| /linux-4.4.14/Documentation/devicetree/bindings/ |
| D | ABI.txt | 24 in the future, we can create a new compatible string. See I.
|
| /linux-4.4.14/drivers/lguest/ |
| D | README | 4 5000-line projects which offer both such capability and glimpses of future
|
| /linux-4.4.14/Documentation/ |
| D | men-chameleon-bus.txt | 78 possible future variant. While parsing the table's entries new MCB devices
87 per MCB device. But this is likely going to change in the future.
|
| D | rtc.txt | 31 only issue an alarm up to 24 hours in the future, other hardware may
158 future, or if there is a leading +=, seconds ahead of the current
176 24 hours in the future. (Use RTC_WKALM_* by preference.)
|
| D | unshare.txt | 109 allowed incremental context unsharing in future without an ABI change.
111 unshare interface should accommodate possible future addition of
291 process is even more complex. If in the future there is a specific
|
| D | robust-futex-ABI.txt | 176 future kernel configuration changes) elements.
182 Bit 29 (0x20000000) of the 'lock word' is reserved for future use.
|
| D | gdb-kernel-debugging.txt | 78 Make breakpoint pending on future shared library load? (y or [n]) y
|
| D | adding-syscalls.txt | 53 interface on the kernel mailing list, and it's important to plan for future
62 way to allow for future extensibility is to include a flags argument to the
74 that is passed in by pointer. Such a structure can cope with future extension
514 size field for future extensibility: https://lkml.org/lkml/2015/7/30/117
|
| D | pnp.txt | 137 Plug and Play but it is planned to be in the near future.
|
| D | magic-number.txt | 22 Please follow this discipline when you are adding future enhancements
|
| D | lzo.txt | 14 for future bug reports.
|
| D | padata.txt | 145 At some point in the future, padata_do_serial() will trigger a call to the
|
| D | vgaarbiter.txt | 82 types in the future, even if the current kernel implementation doesn't.
|
| D | bcache.txt | 77 but will allow for mirroring of metadata and dirty data in the future. Your new
103 The backing device will still use that cache set if it shows up in the future,
|
| D | kmemleak.txt | 194 values. In a future version, kmemleak could only scan the pointer
|
| D | sysfs-rules.txt | 17 the following rules and then your programs should work with future
|
| D | stable_api_nonsense.txt | 138 come back at some future time accidentally. If the internal interfaces
|
| D | robust-futexes.txt | 177 current->robust_list. [Note that in the future, if robust futexes become
|
| D | edac.txt | 22 *can* but must not necessarily be a predictor of future UE events. With
600 Nehalem EDAC driver. They will likely be changed on future versions
|
| D | SubmittingPatches | 543 hopefully inspires them to help us again in the future. Please note that if
550 future patches, and ensures credit for the testers.
591 future.
|
| D | remoteproc.txt | 221 * future), the number of available resource entries, and their offsets
|
| /linux-4.4.14/Documentation/sound/oss/ |
| D | PSS-updates | 59 flag can also be useful in that future versions of this driver may reset all
61 specifying it now will ensure that all future versions of this driver will
|
| D | README.ymfsb | 50 These options will change in future...
|
| /linux-4.4.14/Documentation/networking/ |
| D | openvswitch.txt | 36 applications to work with any version of the flow key, past or future.
123 identify the flow for all future operations. However, when reporting the
131 some but not all of them. However, this behavior may change in future versions.
143 future operations. The kernel is not required to index flows by the original
|
| D | altera_tse.txt | 30 The SGDMA component is to be deprecated in the near future (over the next 1-2
41 Scatter-gather DMA will be added to a future maintenance update to this
47 tested for 1Gbps. This support will be added in a future maintenance update.
85 for transmit operations, but will be added in a future maintenance release.
|
| D | cxacru.txt | 30 the ADSL connection when any value is set. These are logged for future
|
| D | rds.txt | 24 UDP in the future.
190 unused, for future use
|
| D | vrf.txt | 49 future release.
53 Will revisit this limitation in a future release.
|
| D | filter.txt | 600 instruction set, however, future work will migrate other JIT compilers as well,
711 in the future.
797 In the future an eBPF verifier can be used to validate internal BPF programs.
861 BPF_RET 0x06 [ class 6 unused, for future if needed ]
929 unused and reserved for future use.
|
| D | de4x5.txt | 103 products may use it in the future.
|
| D | netdev-FAQ.txt | 29 Linus, and net-next is where the new code goes for the future release.
|
| /linux-4.4.14/tools/perf/Documentation/ |
| D | perf-buildid-cache.txt | 16 files to/from the cache. In the future it should as well set upper limits for
|
| /linux-4.4.14/Documentation/sound/alsa/soc/ |
| D | pops_clicks.txt | 19 currently, however future audio codec hardware will have better pop and click
|
| /linux-4.4.14/fs/quota/ |
| D | Kconfig | 37 future. Please use notification via netlink socket instead.
|
| /linux-4.4.14/Documentation/netlabel/ |
| D | lsm_interface.txt | 44 identifier with the network packet's label. This means that in the future
|
| D | draft-ietf-cipso-ipsecurity-01.txt | 57 defined in future RFCs.
169 The standard format for all current and future CIPSO tags is shown below:
|
| /linux-4.4.14/drivers/staging/ |
| D | Kconfig | 11 future.
|
| /linux-4.4.14/include/uapi/sound/ |
| D | asoc.h | 23 #error kernel release, it will be enabled in a future kernel version
|
| /linux-4.4.14/Documentation/scsi/ |
| D | g_NCR5380.txt | 37 time. More info to come in the future.
|
| D | osd.txt | 169 only deployed OSD transport. In the future we anticipate SAS and FC attached OSD
|
| D | FlashPoint.txt | 150 expect to have some data to report in the not too distant future.
|
| D | scsi_mid_low_api.txt | 90 functions at some point in the future. The LLD will supply
344 make their future removal easier, for example:
1160 * could be re-attached in the future in which case a new instance
1161 * of struct scsi_device would be supplied by future slave_alloc()
|
| D | BusLogic.txt | 27 support any future MultiMaster designs with little or no modification. More
312 possible future I/O port conflicts. The older BT-946C/956C/956CD also have
|
| /linux-4.4.14/Documentation/vm/ |
| D | overcommit-accounting | 24 memory allocations will be available in the future
|
| D | balance | 52 zones in the future.
|
| D | hwpoison.txt | 5 kill the processes associated with it and avoid using it in the future.
|
| D | userfaultfd.txt | 105 single bidirectional socket but in the future two different sockets
|
| D | transhuge.txt | 13 future it can expand over the pagecache layer starting with tmpfs.
192 The transparent_hugepage/enabled values only affect future
|
| /linux-4.4.14/arch/powerpc/platforms/embedded6xx/ |
| D | Kconfig | 16 KuroboxHG has been tested. In the future classical Kurobox,
|
| /linux-4.4.14/Documentation/fb/ |
| D | api.txt | 174 __u16 reserved[2]; /* Reserved for future compatibility */
218 __u32 reserved[4]; /* Reserved for future compatibility */
301 drivers must ignore them. Values other than 0 may get a meaning in future
|
| D | udlfb.txt | 48 In the future, hopefully fbdev will be enhanced with an small standard
53 * It's not clear what the future of fbdev is, given the rise of KMS/DRM.
|
| D | framebuffer.txt | 106 For the future it is planned that frame buffer drivers for graphics cards and
|
| /linux-4.4.14/Documentation/devicetree/bindings/crypto/ |
| D | fsl-sec2.txt | 31 remaining bits are reserved for future SEC EUs.
|
| /linux-4.4.14/Documentation/prctl/ |
| D | no_new_privs.txt | 53 In the future, other potentially dangerous kernel features could become
|
| D | seccomp_filter.txt | 211 that only exists in future kernels will be correctly emulated (by
217 condition: future kernels may improve vsyscall emulation and current
|
| /linux-4.4.14/arch/powerpc/platforms/40x/ |
| D | Kconfig | 95 # OAK doesn't exist but wanted to keep this around for any future 403GCX boards
|
| /linux-4.4.14/drivers/net/wireless/ath/ath9k/ |
| D | ar9003_eeprom.h | 277 u8 future[MAX_BASE_EXTENSION_FUTURE]; member
|
| D | Kconfig | 92 This is currently only a placeholder for future DFS support,
|
| D | ar9003_eeprom.c | 142 .future = {0, 0},
720 .future = {0, 0},
1299 .future = {0, 0},
1878 .future = {0, 0},
2456 .future = {0, 0},
|
| /linux-4.4.14/Documentation/sound/alsa/ |
| D | Bt87x.txt | 40 or not, so that future versions of this driver know about your card.
|
| D | Procfile.txt | 181 can fix it in future kernel releases.
|
| D | compress_offload.txt | 202 are lost during transmission. This may be added in the future.
|
| /linux-4.4.14/Documentation/arm/ |
| D | memory.txt | 85 Since future CPUs may impact the kernel mapping layout, user programs
|
| D | kernel_mode_neon.txt | 84 kernel is currently compiled at -O2, future changes may result in NEON/VFP
|
| D | Interrupts | 12 allow more flexible TLB handling for the future.
|
| D | README | 81 memory management, architecture definitions etc). For all future
|
| /linux-4.4.14/Documentation/networking/mac80211_hwsim/ |
| D | README | 23 and always reproduce the same setup for future tests. In addition,
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/ |
| D | fw-cfg.txt | 59 * Further registers may be appended to the region in case of future interface
|
| /linux-4.4.14/Documentation/accounting/ |
| D | taskstats.txt | 12 - extensibility for use by future accounting patches
138 in future:
|
| /linux-4.4.14/Documentation/usb/ |
| D | bulk-streams.txt | 52 controller driver, and may change in the future.
|
| D | URB.txt | 216 disabled, but in the future this will be changed, so don't assume that
|
| /linux-4.4.14/Documentation/filesystems/nfs/ |
| D | idmapper.txt | 34 The last parameter, 600, defines how many seconds into the future the key will
|
| D | pnfs.txt | 95 (More protocols can be defined in the future.
|
| D | nfs41-server.txt | 145 NFS4ERR_ENCR_ALG_UNSUPP on EXCHANGE_ID, which should be future-proof.
|
| D | knfsd-stats.txt | 103 to allow for future spikes in load.
|
| /linux-4.4.14/Documentation/fmc/ |
| D | carrier.txt | 22 still change in the future. For this reason, there is a version field
197 but fmc-specific flags may be added in the future. You'll most
211 reserved to fit bigger I2C devices in the future. Carriers may
|
| D | FMC-and-SDB.txt | 81 plan to submit it upstream in the future, and don't want to force
|
| /linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/ |
| D | qe.txt | 11 more nodes and properties would be extended in the future.
|
| /linux-4.4.14/Documentation/PCI/ |
| D | pci-iov-howto.txt | 44 The second method is the recommended method for new/future VF devices.
|
| /linux-4.4.14/Documentation/input/ |
| D | xpad.txt | 15 the future could be supported.
88 box in the future.
|
| D | joystick.txt | 431 future if I get an Amiga in the reach of my fingers.
476 but in the future, Logitech CyberMan (the original one, not CM2) could be
|
| D | input.txt | 33 devices, future use (say 2.5/2.6) is expected to expand to replace
|
| /linux-4.4.14/Documentation/RCU/ |
| D | lockdep.txt | 101 being in an RCU read-side critical section. In the future, separate
|
| /linux-4.4.14/Documentation/block/ |
| D | ioprio.txt | 25 process needs the disk for on each service. In the future this might change
|
| /linux-4.4.14/Documentation/arm/nwfpe/ |
| D | TODO | 21 be implemented in future versions.
|
| D | README.FPE | 138 be implemented in future versions.
|
| /linux-4.4.14/tools/virtio/virtio-trace/ |
| D | README | 110 be solved in the future.
|
| /linux-4.4.14/Documentation/cgroups/ |
| D | cgroups.txt | 41 tasks, and all their future children, into hierarchical groups with
215 hierarchy. This may be possible in future, but is fraught with nasty
376 the future.
387 cgroup hierarchy is intended to be implemented in the future.
600 attach() or cancel_attach() will be called in future.
|
| /linux-4.4.14/Documentation/arm/Marvell/ |
| D | README | 135 Linux kernel mach directory: no code in mainline yet, planned for the future
136 Linux kernel plat directory: no code in mainline yet, planned for the future
|
| /linux-4.4.14/Documentation/power/ |
| D | pm_qos_interface.txt | 43 Clients of pm_qos need to save the returned handle for future use in other
114 Clients of dev_pm_qos need to save the handle for future use in other
|
| D | runtime_pm.txt | 320 to suspend the device again in future and -EACCES means that
333 resume the device again in future, but 'power.runtime_error' should be
349 device in future, where 'delay' is the time to wait before queuing up a
628 likely it would need a runtime resume in the near future anyway.
837 in the future (as it normally would be if the callback invoked
|
| D | power_supply_class.txt | 186 Good candidates to add in future: model/part#, cycle_time, manufacturer,
|
| D | userland-swsusp.txt | 126 by the kernel and its structure may be changed in future kernel releases.
|
| /linux-4.4.14/Documentation/devicetree/bindings/bus/ |
| D | ti-gpmc.txt | 33 As this will change in the future, filling correct
|
| /linux-4.4.14/Documentation/networking/dsa/ |
| D | bcm_sf2.txt | 63 may change in the future.
|
| /linux-4.4.14/drivers/pinctrl/ |
| D | Kconfig | 34 future processors. This option is selected automatically when specific
|
| /linux-4.4.14/Documentation/arm/Samsung-S3C24XX/ |
| D | GPIO.txt | 27 in the near future).
|
| D | Overview.txt | 132 be configured for it in one kernel build, and any future additions
|
| /linux-4.4.14/Documentation/gpio/ |
| D | board.txt | 132 In the future, these flags might be extended to support more properties.
|
| /linux-4.4.14/Documentation/trace/ |
| D | events-kmem.txt | 104 high-order allocations will start failing at some time in the future. One
|
| /linux-4.4.14/Documentation/timers/ |
| D | highres.txt | 218 reprograms the sched_tick to this future event, to allow longer idle sleeps
239 frequency profiling, and a complete removal of jiffies in the future.
|
| /linux-4.4.14/Documentation/laptops/ |
| D | sony-laptop.txt | 140 future, sonypi will be removed and replaced by sony-laptop.
|
| D | sonypi.txt | 34 commands may be added in the future).
|
| /linux-4.4.14/Documentation/aoe/ |
| D | aoe.txt | 54 In the future these character devices may disappear and be replaced
|
| /linux-4.4.14/Documentation/hid/ |
| D | hidraw.txt | 24 and Bluetooth. In the future, as new hardware bus types are developed which
|
| /linux-4.4.14/Documentation/target/ |
| D | tcmu-design.txt | 83 - Allow future flexibility in user & kernel implementations
169 More opcodes may be added in the future. If userspace encounters an
|
| /linux-4.4.14/Documentation/x86/ |
| D | pat.txt | 149 today, but may be enforced in future.
|
| D | intel_mpx.txt | 222 into struct mm_struct to be used in future during PR_MPX_ENABLE_MANAGEMENT
|
| /linux-4.4.14/Documentation/development-process/ |
| D | 6.Followthrough | 71 can help future reviewers avoid the questions which came up the first time
159 well make it harder for you to get work merged in the future.
|
| D | 7.AdvancedTopics | 115 can affect your ability to get trees pulled in the future. Quoting Linus:
|
| /linux-4.4.14/fs/cramfs/ |
| D | README | 93 PAGE_CACHE_SIZE may grow in future (if I interpret the comment
|
| /linux-4.4.14/Documentation/video4linux/ |
| D | README.ivtv | 126 device in the future.
|
| D | README.pvrusb2 | 43 Linux APIs (V4L, sysfs, maybe DVB in the future).
|
| /linux-4.4.14/Documentation/blockdev/ |
| D | ramdisk.txt | 121 required, but may be in the future.) It is wise to zero out the
|
| /linux-4.4.14/Documentation/spi/ |
| D | spidev | 34 devices. That mechanism might be supported here in the future.)
|
| /linux-4.4.14/arch/arm/kernel/ |
| D | head.S | 532 @ If a future SoC *does* use 0x0 as the PERIPH_BASE, then the
|
| /linux-4.4.14/Documentation/leds/ |
| D | ledtrig-transient.txt | 114 at the set value to be used when activate is set at a future time. This will
|
| /linux-4.4.14/Documentation/driver-model/ |
| D | driver.txt | 136 A future feature of this directory will be a 'devices' directory. This
|
| /linux-4.4.14/Documentation/watchdog/ |
| D | watchdog-api.txt | 31 future driver writers to use it as a reference.
|
| /linux-4.4.14/arch/x86/kernel/ |
| D | head_32.S | 436 movb %al,%cl # save reg for future use
|
| /linux-4.4.14/arch/m68k/ifpsp060/src/ |
| D | isp.S | 889 # future access error; if -(a7), set mda7_flg in #
893 # future access error; if (a7)+, set mia7_flg in #
|
| /linux-4.4.14/Documentation/i2c/ |
| D | dev-interface | 189 checking on future transactions.)
|
| /linux-4.4.14/fs/affs/ |
| D | Changes | 80 - locking should be safe for the future
|
| /linux-4.4.14/fs/reiserfs/ |
| D | README | 10 and likely will be in the future, licensed to other parties under
|
| /linux-4.4.14/Documentation/scheduler/ |
| D | completion.txt | 208 or calls complete_all() to signal all current and future waiters.
|
| D | sched-design-CFS.txt | 54 runqueues, but it uses a time-ordered rbtree to build a "timeline" of future
|
| /linux-4.4.14/Documentation/filesystems/caching/ |
| D | netfs-api.txt | 437 some point in the future, and as such, it may happen after the function returns
808 size of the file to allow for future file expansion.
867 cancelled and discarded. Some future operations will be rejected until the
|
| /linux-4.4.14/tools/usb/usbip/ |
| D | INSTALL | 23 you can run in the future to recreate the current configuration, and a
|
| /linux-4.4.14/drivers/media/usb/dvb-usb/ |
| D | Kconfig | 129 shall be added in the future. Devices that require this module:
|
| /linux-4.4.14/arch/m68k/ |
| D | Kconfig.cpu | 301 At some point in the future, this will cause floating-point math
|
| /linux-4.4.14/arch/arc/ |
| D | Kconfig | 455 in future
|
| /linux-4.4.14/Documentation/ioctl/ |
| D | botching-up-ioctls.txt | 70 future extensions is going right down the gutters since someone will submit
|
| /linux-4.4.14/arch/x86/ |
| D | Kconfig.debug | 328 decision will become the default in the future. Until then this option
|
| /linux-4.4.14/Documentation/nvdimm/ |
| D | nvdimm.txt | 534 3. What if a third major interface type arises in the future? Outside
543 future-proof.
|
| /linux-4.4.14/drivers/tty/serial/8250/ |
| D | Kconfig | 23 in the future.]
|
| /linux-4.4.14/Documentation/device-mapper/ |
| D | cache.txt | 288 value, in the future a variant message that takes cblock ranges
|