/linux-4.4.14/Documentation/ABI/testing/ |
D | sysfs-devices | 11 Please do not rely on the format of this tree because of 13 the tree, please use the /sys/class structure and rely 16 Or rely on the uevent messages to notify programs of
|
D | sysfs-firmware-dmi-entries | 10 The kernel itself does not rely on the majority of the
|
/linux-4.4.14/drivers/input/mouse/ |
D | maplemouse.c | 28 int buttons, relx, rely, relz; in dc_mouse_callback() local 36 rely = *(unsigned short *)(res + 14) - 512; in dc_mouse_callback() 43 input_report_rel(dev, REL_Y, rely); in dc_mouse_callback()
|
/linux-4.4.14/fs/notify/dnotify/ |
D | Kconfig | 8 superior alternatives, but some applications may still rely on
|
/linux-4.4.14/Documentation/ABI/ |
D | README | 26 programs can start to rely on these interfaces, but they must be 80 - Kconfig. Userspace should not rely on the presence or absence of any 85 - Kernel-internal symbols. Do not rely on the presence, absence, location, or
|
/linux-4.4.14/fs/sysfs/ |
D | Kconfig | 15 Some system agents rely on the information in sysfs to operate.
|
/linux-4.4.14/Documentation/arm/ |
D | swp_emulation | 22 NOTE: when accessing uncached shared regions, LDREX/STREX rely on an external
|
D | kernel_mode_neon.txt | 6 * Use only NEON instructions, or VFP instructions that don't rely on support 67 Earlier versions of VFP (prior to version 3) rely on software support for things
|
D | mem_alignment | 9 Of course this is a bad idea to rely on the alignment trap to perform
|
D | Porting | 6 The following symbol definitions rely on you knowing the translation that
|
D | cluster-pm-race-avoidance.txt | 32 mechanisms like Linux spinlocks may rely on coherency mechanisms which
|
/linux-4.4.14/Documentation/accounting/ |
D | cgroupstats.txt | 17 NOTE: We currently rely on delay accounting for extracting information
|
/linux-4.4.14/Documentation/arm64/ |
D | tagged-pointers.txt | 23 of tags cannot rely on the tag information for user virtual
|
/linux-4.4.14/Documentation/ABI/stable/ |
D | sysfs-firmware-opal-dump | 20 Do not rely on any particular size of dump
|
/linux-4.4.14/Documentation/power/ |
D | apm-acpi.txt | 24 Both APM and ACPI rely on user-space daemons, apmd and acpid
|
D | video.txt | 34 hard/impossible. Methods that do not rely on userland are preferable.
|
/linux-4.4.14/Documentation/devicetree/bindings/mtd/ |
D | gpmi-nand.txt | 29 area with the byte in the data area but rely on the
|
/linux-4.4.14/drivers/media/v4l2-core/ |
D | Kconfig | 24 Only useful if you rely on the old behavior and use mknod instead of udev.
|
/linux-4.4.14/Documentation/i2c/ |
D | summary | 14 achieve I2C branding. Modern PC mainboards rely on SMBus. The most common
|
D | fault-codes | 18 to respond correctly. Other code may need to rely on YOUR code reporting 53 host. Note that even if PECs are in use, you should not rely
|
/linux-4.4.14/Documentation/filesystems/ |
D | ceph.txt | 21 In contrast to cluster filesystems like GFS, OCFS2, and GPFS that rely 119 must rely on TCP's error correction to detect data corruption
|
D | porting | 462 taken anymore, so verify that your callbacks do not rely on it (none
|
D | spufs.txt | 155 programs should not rely on them because access to any of them except
|
/linux-4.4.14/arch/arm/boot/dts/ |
D | sun8i-a23-ippo-q8h-v1.2.dts | 53 * FIXME for now we only support host mode and rely on u-boot to have
|
D | sun8i-a33-q8-tablet.dts | 53 * FIXME for now we only support host mode and rely on u-boot to have
|
D | sun8i-a23-q8-tablet.dts | 53 * FIXME for now we only support host mode and rely on u-boot to have
|
D | sun8i-a23-ippo-q8h-v5.dts | 53 * FIXME for now we only support host mode and rely on u-boot to have
|
D | sun8i-a33-ippo-q8h-v1.2.dts | 53 * FIXME for now we only support host mode and rely on u-boot to have
|
D | sun8i-a33-et-q8-v1.6.dts | 53 * FIXME for now we only support host mode and rely on u-boot to have
|
D | sun8i-a23-gt90h-v4.dts | 133 * FIXME for now we only support host mode and rely on u-boot to have
|
/linux-4.4.14/drivers/nvdimm/ |
D | Kconfig | 64 applications that rely on sector writes not being torn (a
|
/linux-4.4.14/Documentation/fmc/ |
D | fmc-chardev.txt | 12 fdelay-0400 if the FMC core can rely on both a mezzanine name and a bus
|
D | mezzanine.txt | 82 The parameters are carrier-specific, in that they rely on the busid
|
/linux-4.4.14/Documentation/hwmon/ |
D | ltc4245 | 43 rely on the sense resistors listed in Table 2: "Sense Resistor Values".
|
/linux-4.4.14/arch/arm/crypto/ |
D | Kconfig | 101 This implementation does not rely on any lookup tables so it is
|
/linux-4.4.14/Documentation/arm/Samsung-S3C24XX/ |
D | Suspend.txt | 92 rely on are still enabled at that point.
|
/linux-4.4.14/Documentation/parisc/ |
D | registers | 105 since the caller can't rely on the value being the same
|
/linux-4.4.14/Documentation/ |
D | unaligned-memory-access.txt | 93 Therefore, for standard structure types you can always rely on the compiler 97 Similarly, you can also rely on the compiler to align variables and function
|
D | preempt-locking.txt | 123 in doubt, rely on locking or explicit preemption disabling.
|
D | cpu-hotplug.txt | 63 should only rely on this to count the # of cpus, but *MUST* not rely
|
D | circular-buffers.txt | 187 is actually awakened. We therefore cannot rely on it for ordering. However,
|
D | clk.txt | 233 clocks properly but rely on them being on from the bootloader, bypassing
|
D | sysfs-rules.txt | 39 interfaces, and such that you can rely on in userspace. Everything is
|
D | rbtree.txt | 208 you are not expected to rely on; please stick to the documented APIs
|
D | initrd.txt | 313 Current kernels still support it, but you should _not_ rely on its
|
D | HOWTO | 63 people on the mailing lists are not lawyers, and you should not rely on
|
D | memory-barriers.txt | 742 You must also be careful not to rely too much on boolean short-circuit
|
D | kernel-parameters.txt | 1575 as thermal controls and power capping, that rely on ACPI
|
/linux-4.4.14/arch/arm/kernel/ |
D | entry-header.S | 85 @ we cannot rely on r0-r3 and r12 matching the value saved in the
|
/linux-4.4.14/Documentation/usb/ |
D | hotplug.txt | 29 Because some of those actions rely on information about drivers (metadata)
|
D | URB.txt | 10 complete; don't rely on it except for a quick overview.
|
D | proc_usb_info.txt | 49 you can't rely on them for stable access to devices. For example,
|
/linux-4.4.14/Documentation/gpio/ |
D | gpio.txt | 32 System-on-Chip (SOC) processors heavily rely on GPIOs. In some cases, every
|
D | driver.txt | 197 callbacks from the GPIO and irqchip APIs. Do not rely on gpiod_to_irq() having
|
D | gpio-legacy.txt | 19 System-on-Chip (SOC) processors heavily rely on GPIOs. In some cases, every 154 idea to rely on boot firmware to have set the direction correctly, since
|
/linux-4.4.14/Documentation/pcmcia/ |
D | driver-changes.txt | 123 driver was reported to rely on them:
|
/linux-4.4.14/arch/mips/ |
D | Kconfig.debug | 52 Most MIPS systems will normally expect 'N' here and rely upon
|
/linux-4.4.14/Documentation/scheduler/ |
D | sched-rt-group.txt | 42 Realtime scheduling is all about determinism, a group has to be able to rely on
|
D | sched-design-CFS.txt | 88 CFS uses nanosecond granularity accounting and does not rely on any jiffies or
|
/linux-4.4.14/Documentation/video4linux/ |
D | soc-camera.txt | 135 rely on camera drivers implementing .cropcap(). If the camera driver does not
|
/linux-4.4.14/Documentation/networking/ |
D | regulatory.txt | 77 *Most* drivers will rely on the first mechanism of providing a
|
D | rds.txt | 135 forever if you rely on poll to tell you what to do.
|
D | vortex.txt | 347 reproduce problems and must rely on your patience and efforts to get to
|
D | ppp_generic.txt | 163 algorithms rely on receiving compressed packets in the same order that
|
D | arcnet.txt | 433 schemes that rely completely on the netmask and a 'default gateway' to
|
D | can.txt | 381 kernel interfaces (ABI) which heavily rely on the CAN frame with fixed eight
|
D | bonding.txt | 790 a concern use this variable to disable flow shuffling and rely on 1923 then the MII monitor will rely on the driver for carrier state
|
D | ip-sysctl.txt | 350 only to prevent simple DoS attacks, you _must_ not rely on this
|
/linux-4.4.14/Documentation/fb/ |
D | udlfb.txt | 76 code. They write to the standard framebuffer interface and rely on udlfb
|
/linux-4.4.14/Documentation/driver-model/ |
D | platform.txt | 122 original IBM PCs, rely on error-prone "probe-the-hardware" models for hardware
|
/linux-4.4.14/Documentation/prctl/ |
D | seccomp_filter.txt | 209 rip or rsp. (Do not rely on other changes terminating the process.
|
/linux-4.4.14/Documentation/input/ |
D | input-programming.txt | 259 rely on kernel's default implementation of setting and querying keycode
|
/linux-4.4.14/Documentation/sound/alsa/ |
D | timestamping.txt | 9 and precise moment. Applications should not rely solely on the first
|
/linux-4.4.14/Documentation/hid/ |
D | uhid.txt | 18 dynamically so you need to rely on udev (or similar) to create the device node.
|
/linux-4.4.14/Documentation/virtual/kvm/ |
D | msr.txt | 199 type 1 was, but guest should not rely on that.
|
/linux-4.4.14/Documentation/ia64/ |
D | mca.txt | 35 handlers cannot rely on the thread pointer, PAL physical mode can
|
D | fsys.txt | 188 words, user-level code must not rely on PSR.be being preserved
|
/linux-4.4.14/arch/tile/ |
D | Kconfig | 361 to not rely on the boot loader to provide them.)
|
/linux-4.4.14/Documentation/nvdimm/ |
D | btt.txt | 19 persistent memory devices, so that applications that rely on sector writes not
|
D | nvdimm.txt | 539 region-types. Userspace can always rely on the generic region
|
/linux-4.4.14/Documentation/ioctl/ |
D | botching-up-ioctls.txt | 57 extension is supported on a given kernel. If you can't rely on old kernels
|
/linux-4.4.14/arch/x86/ |
D | Kconfig.debug | 352 This might help diagnose strange hangs that rely on NMI to
|
D | Kconfig | 2087 to not rely on the boot loader to provide them.)
|
/linux-4.4.14/Documentation/device-mapper/ |
D | thin-provisioning.txt | 32 do not yet rely on them in production. But do experiment and offer us
|
/linux-4.4.14/drivers/net/usb/ |
D | Kconfig | 134 "Laplink" parallel cables or some motherboards. These rely
|
/linux-4.4.14/scripts/dtc/ |
D | dtc-parser.tab.c_shipped | 783 /* Print *YYLOCP on YYO. Private, do not rely on its existence. */ 1455 users should not rely upon it. Assigning to YYVAL
|
/linux-4.4.14/arch/arm64/ |
D | Kconfig | 620 NOTE: when accessing uncached shared regions, LDXR/STXR rely
|
/linux-4.4.14/Documentation/scsi/ |
D | BusLogic.txt | 29 costly and rely on the host CPU, rather than including an onboard processor.
|
D | ChangeLog.lpfc | 1561 routines. Remove generic'ness and rely on set attribute.
|
/linux-4.4.14/arch/arm/mm/ |
D | Kconfig | 706 NOTE: when accessing uncached shared regions, LDREX/STREX rely
|
/linux-4.4.14/drivers/ide/ |
D | Kconfig | 192 files in sysfs but many legacy applications rely on this.
|
/linux-4.4.14/drivers/scsi/aic7xxx/ |
D | aic79xx.seq | 561 * selection so we can rely on it even for case #1 above. 1614 * rely on the SCB_RESID* fields. Initialize the
|
/linux-4.4.14/Documentation/filesystems/caching/ |
D | netfs-api.txt | 218 length. A netfs mustn't rely on being able to provide more than 400 bytes
|
/linux-4.4.14/scripts/genksyms/ |
D | parse.tab.c_shipped | 1672 users should not rely upon it. Assigning to YYVAL
|
/linux-4.4.14/scripts/kconfig/ |
D | zconf.tab.c_shipped | 1673 users should not rely upon it. Assigning to YYVAL
|
/linux-4.4.14/Documentation/block/ |
D | biodoc.txt | 705 transfer in one go unless it interprets segments), and rely on the block layer
|
/linux-4.4.14/drivers/hwmon/ |
D | Kconfig | 1676 files which may change in the future, so you shouldn't rely
|
/linux-4.4.14/drivers/scsi/ |
D | Kconfig | 66 files in sysfs but many legacy applications rely on this.
|
/linux-4.4.14/init/ |
D | Kconfig | 555 for context tracking and the subsystems that rely on it: RCU
|
/linux-4.4.14/Documentation/RCU/ |
D | RTFP.txt | 270 RCU-like usage that does not rely on an automatic garbage
|
/linux-4.4.14/drivers/video/fbdev/ |
D | Kconfig | 201 Generalized Timing Formula and the EDID parser. A few drivers rely
|