| /linux-4.1.27/drivers/media/pci/ivtv/ |
| D | ivtvfb.c | 393 u16 lead = 0, tail = 0; in ivtvfb_write() local
428 lead = 4 - ((unsigned long)dst & 3); in ivtvfb_write()
429 if (copy_from_user(dst, buf, lead)) in ivtvfb_write()
431 buf += lead; in ivtvfb_write()
432 dst += lead; in ivtvfb_write()
435 if ((count - lead) & 3) in ivtvfb_write()
436 tail = (count - lead) & 3; in ivtvfb_write()
438 dma_size = count - lead - tail; in ivtvfb_write()
440 p + lead + dma_offset, (void __user *)buf, dma_size); in ivtvfb_write()
|
| /linux-4.1.27/Documentation/ide/ |
| D | warm-plug-howto.txt | 18 results may be unpredictable and lead to data loss if you're unlucky
|
| /linux-4.1.27/Documentation/devicetree/bindings/media/i2c/ |
| D | adv7343.txt | 3 The ADV7343 are high speed, digital-to-analog video encoders in a 64-lead LQFP
|
| /linux-4.1.27/Documentation/hwmon/ |
| D | adm1026 | 88 voltage from the power lead rather than on the ground lead.
|
| D | w83791d | 54 chip appears to be the same as the W83791D but is lead free.
|
| D | lm90 | 201 * The G variant is lead-free, otherwise similar to the W.
|
| /linux-4.1.27/drivers/eisa/ |
| D | Kconfig | 27 # an X86 may lead to crashes...
|
| /linux-4.1.27/security/tomoyo/ |
| D | Kconfig | 48 operations which can lead to the hijacking of the boot sequence are
|
| /linux-4.1.27/Documentation/ |
| D | cpu-load.txt | 51 will lead to quite erratic information inside `/proc/stat'.
|
| D | flexible-arrays.txt | 40 the current code, using flags to ask for high memory is likely to lead to
|
| D | iostats.txt | 146 eventual merges. As requests can be merged across partition, this could lead
|
| D | kmemleak.txt | 189 address inside a block's address range. This may lead to an increased
|
| D | crc32.txt | 59 These details lead to a standard trick: rearrange merging in the
|
| D | unaligned-memory-access.txt | 127 lead to unaligned accesses when accessing fields that do not satisfy
|
| D | kmemcheck.txt | 60 Without this, gcc will use certain optimizations that usually lead to
647 that the allocation should not be tracked because it would lead to
|
| D | ManagementStyle | 15 lead persons, not the people who do traditional management inside
|
| D | edac.txt | 463 system context might be so mangled that continuing will lead to further
|
| D | SubmittingPatches | 373 or questions that do not lead to a code change should almost certainly
|
| /linux-4.1.27/scripts/ |
| D | checkpatch.pl | 4801 my $lead = $fixed[$fixlinenr] =~
4803 $lead = rtrim($1);
4804 $lead = "$lead " if ($lead !~ /^\+$/);
4805 $lead = "${lead}const ";
4806 $fixed[$fixlinenr] =~ s/(^\+\s*(?:static\s+))/$lead/;
5300 my $lead = $1;
|
| /linux-4.1.27/scripts/coccinelle/null/ |
| D | badzero.cocci | 119 // This rule may lead to inconsistent path problems, if E is defined in two
|
| /linux-4.1.27/Documentation/misc-devices/ |
| D | apds990x.txt | 29 lead to false interrupt, but that doesn't harm.
|
| /linux-4.1.27/Documentation/device-mapper/ |
| D | dm-crypt.txt | 61 option. For example, allowing discards on encrypted devices may lead to
|
| /linux-4.1.27/Documentation/locking/ |
| D | lockdep-design.txt | 81 The same lock-class must not be acquired twice, because this could lead
89 because this could lead to lock inversion deadlocks. (The validator
127 could lead to a lock inversion deadlock - even if that lock scenario did
|
| /linux-4.1.27/Documentation/acpi/ |
| D | video_extension.txt | 92 so this would lead to the same effect as case i) now.
|
| /linux-4.1.27/Documentation/power/ |
| D | suspend-and-cpuhotplug.txt | 255 operation in progress. Hence, it will lead to wrong notifications being
257 instead of CPU_ONLINE_FROZEN) which in turn will lead to execution of
|
| D | freezing-of-tasks.txt | 214 that could lead to freezing failures, because if the suspend/hibernate code
|
| D | pci.txt | 826 it should only be used for performing operations that would lead to race
|
| /linux-4.1.27/Documentation/development-process/ |
| D | 7.AdvancedTopics | 75 Excessive use of this capability can lead to other problems, though, beyond
170 All types of review, if they lead to better code going into the kernel, are
|
| D | 3.Early-stage | 16 with the proposed solution, and that can lead to difficulties.
|
| D | 4.Coding | 386 lead to literally hundreds or thousands of changes - many of which are
|
| /linux-4.1.27/Documentation/video4linux/ |
| D | radiotrack.txt | 37 input is simply an antenna lead, and the output is a power audio signal
|
| /linux-4.1.27/Documentation/i2c/busses/ |
| D | i2c-parport | 154 The project has lead to new libs for the Velleman K8000 and K8005:
|
| /linux-4.1.27/Documentation/scheduler/ |
| D | sched-domains.txt | 10 although strictly it doesn't have to, but this could lead to a case where some
|
| D | sched-design-CFS.txt | 193 This function is mostly called from time tick functions; it might lead to
|
| /linux-4.1.27/arch/m68k/fpsp040/ |
| D | setox.S | 505 fmuls #0xBC317218,%fp0 | ...N * L1, L1 = lead(-log2/64)
545 fmovex (%a1)+,%fp1 | ...fp1 is lead. pt. of 2^(J/64)
671 fmuls #0xBC317218,%fp0 | ...N * L1, L1 = lead(-log2/64)
|
| /linux-4.1.27/arch/sh/mm/ |
| D | Kconfig | 61 value on any of the known systems will only lead to disaster.
|
| /linux-4.1.27/Documentation/sound/alsa/ |
| D | Procfile.txt | 116 values, but can be lead to too much corrections for a (mostly
|
| D | Audiophile-Usb.txt | 99 Default Alsa driver mode can lead to device misconfigurations.
246 * Failing to respect this will lead to a misconfiguration of the device. In this case
|
| D | OSS-Emulation.txt | 116 This will lead to some problems for some applications like quake or
|
| /linux-4.1.27/net/ipv6/ |
| D | Kconfig | 227 may sometimes lead to unintended routing behavior. This can be
|
| /linux-4.1.27/drivers/net/ppp/ |
| D | Kconfig | 117 which can lead to bad results if the ATM peer loses state and
|
| /linux-4.1.27/sound/drivers/ |
| D | Kconfig | 49 driver may lead to a problem. Namely, it may get loaded
|
| /linux-4.1.27/fs/jffs2/ |
| D | README.Locking | 55 lead to deadlock, unless we played games with unlocking the i_sem
|
| /linux-4.1.27/Documentation/powerpc/ |
| D | transactional_memory.txt | 77 Performing syscalls from within transaction is not recommended, and can lead
|
| D | eeh-pci-error-recovery.txt | 24 can lead to data corruption, both of user data or of kernel data,
|
| /linux-4.1.27/Documentation/filesystems/ |
| D | ext3.txt | 37 noload mount of inconsistent filesystem, which can lead to
|
| D | btrfs.txt | 154 (non-battery-backed) write-back cache, nobarrier option will lead to
|
| D | autofs4-mount-control.txt | 146 used for this as raw Netlink would lead to a significant increase in
152 that lead to the decision to not use it. This is that the autofs
|
| D | ext4.txt | 156 skipping the journal replay will lead to the
158 lead to any number of problems.
|
| D | xfs-self-describing-metadata.txt | 124 events that lead to the eventual failure, and even whether there are corruptions
|
| D | ext2.txt | 265 than 256 characters, which would lead to corrupt directory listings.
|
| D | Locking | 285 radix tree. This incoherency can lead to all sorts of hard-to-debug problems
|
| D | coda.txt | 352 involves more than one upcall, this can lead to complicated state, an
1461 intercepted by the Coda FS Driver and lead to cache invalidations of
|
| D | xfs-delayed-logging-design.txt | 527 The problem with this is that it can lead to deadlocks as we may need to commit
|
| /linux-4.1.27/Documentation/networking/ |
| D | 6pack.txt | 80 kernels may lead to a compilation error because the interface to a kernel
|
| D | spider_net.txt | 130 it will restart at the next descr. This potentially will lead to a
|
| D | ixgbe.txt | 120 lead to Tx hangs.
|
| D | can.txt | 115 character device, too, but this would lead to a technically inelegant
222 The use of the CAN bus may lead to several problems on the physical
608 lead to multiple filters in the af_can.c filter processing. These filters
|
| D | timestamping.txt | 456 software time stamping and therefore could lead to unexpected deltas
|
| D | z8530drv.txt | 615 lead to delayed answers on interrupts. You can recognize these
|
| D | ip-sysctl.txt | 48 because they could be easily forged and can lead to unwanted
147 reordering of packets occurs, which could lead to poor application
|
| /linux-4.1.27/arch/powerpc/platforms/ |
| D | Kconfig | 254 is buggy and can cause a situation which would lead unexplained hard
|
| /linux-4.1.27/Documentation/cgroups/ |
| D | unified-hierarchy.txt | 211 this direction will lead to problems which will be extremely difficult
373 lead to gradual performance degradation. The user can monitor this
|
| D | cgroups.txt | 145 appropriate network and other resource class. This may lead to
|
| D | memory.txt | 546 there is a swap storage available. This might lead to memcg OOM killer
|
| /linux-4.1.27/arch/xtensa/ |
| D | Kconfig | 450 the correct address. Wrong address here may lead to hardware lockup.
|
| /linux-4.1.27/arch/arm/ |
| D | Kconfig | 1094 bool "ARM errata: Incorrect hazard handling in the SCU may lead to data corruption"
1132 bool "ARM errata: Faulty hazard checking in the Store Buffer may lead to data corruption"
1138 optimisation in the Cortex-A9 Store Buffer may lead to data
1205 bool "ARM errata: A data cache maintenance operation which aborts, might lead to deadlock"
|
| /linux-4.1.27/drivers/atm/ |
| D | Kconfig | 83 Also, sometimes larger bursts lead to lower throughput, e.g. on an
|
| /linux-4.1.27/Documentation/trace/ |
| D | events.txt | 253 result in an unintended mixture of filters which could lead to
|
| /linux-4.1.27/ |
| D | README | 229 under some circumstances lead to problems: probing for a
|
| /linux-4.1.27/Documentation/isdn/ |
| D | README | 388 and lead to a high phone bill! Some daemons or other pc's that use
|
| /linux-4.1.27/Documentation/vm/ |
| D | numa_memory_policy.txt | 310 on the reference count, as this can lead to cache lines bouncing between cpus
|
| /linux-4.1.27/Documentation/laptops/ |
| D | laptop-mode.txt | 771 …ng laptop mode and your battery interface $BATT_INFO is missing. This may lead to loss of data whe…
|
| /linux-4.1.27/Documentation/scsi/ |
| D | scsi_mid_low_api.txt | 407 * this call can lead to slave_alloc() and slave_configure() callbacks
602 * lead to the slave_destroy() callback being invoked. sdev is an
|
| D | BusLogic.txt | 421 that explicitly enabling Tagged Queuing may lead to problems; the option to
|
| /linux-4.1.27/Documentation/netlabel/ |
| D | draft-ietf-cipso-ipsecurity-01.txt | 557 lead to non-interoperability or even a security incident. The
|
| /linux-4.1.27/Documentation/sysctl/ |
| D | vm.txt | 769 lead to out-of-memory conditions. Increasing vfs_cache_pressure beyond 100
|
| /linux-4.1.27/scripts/genksyms/ |
| D | parse.tab.c_shipped | 2181 case of YYERROR or YYBACKUP, subsequent parser actions might lead
|
| /linux-4.1.27/Documentation/m68k/ |
| D | kernel-options.txt | 864 Incorrect use can lead to unpredictable behavior, so please only use
|
| /linux-4.1.27/scripts/kconfig/ |
| D | zconf.tab.c_shipped | 2070 case of YYERROR or YYBACKUP, subsequent parser actions might lead
|
| /linux-4.1.27/scripts/dtc/ |
| D | dtc-parser.tab.c_shipped | 2083 case of YYERROR or YYBACKUP, subsequent parser actions might lead
|
| /linux-4.1.27/drivers/rtc/ |
| D | Kconfig | 886 /proc/drivers/rtc. Keep in mind that this can potentially lead
|
| /linux-4.1.27/Documentation/cdrom/ |
| D | cdrom-standard.tex | 904 various digital information has lead to many different disc types.
|
| /linux-4.1.27/drivers/hwmon/ |
| D | Kconfig | 1678 This driver also supports the W83627EHG, which is the lead-free
|
| /linux-4.1.27/drivers/scsi/aic7xxx/ |
| D | aic79xx.seq | 1839 * This can lead to the restoration of a
|
| /linux-4.1.27/arch/m68k/ifpsp060/src/ |
| D | fplsp.S | 7145 fmul.s &0xBC317218,%fp0 # N * L1, L1 = lead(-log2/64)
7181 fmov.x (%a1)+,%fp1 # fp1 is lead. pt. of 2^(J/64)
7307 fmul.s &0xBC317218,%fp0 # N * L1, L1 = lead(-log2/64)
|
| /linux-4.1.27/arch/x86/ |
| D | Kconfig | 1557 can lead to all sorts of problems, so it's good to say Y here.
|