Home
last modified time | relevance | path

Searched refs:lead (Results 1 – 25 of 114) sorted by relevance

12345

/Linux-v4.19/drivers/media/pci/ivtv/
Divtvfb.c386 u16 lead = 0, tail = 0; in ivtvfb_write() local
421 lead = 4 - ((unsigned long)dst & 3); in ivtvfb_write()
422 if (copy_from_user(dst, buf, lead)) in ivtvfb_write()
424 buf += lead; in ivtvfb_write()
425 dst += lead; in ivtvfb_write()
428 if ((count - lead) & 3) in ivtvfb_write()
429 tail = (count - lead) & 3; in ivtvfb_write()
431 dma_size = count - lead - tail; in ivtvfb_write()
433 p + lead + dma_offset, (void __user *)buf, dma_size); in ivtvfb_write()
/Linux-v4.19/Documentation/ABI/obsolete/
Dsysfs-firmware-acpi7 the offline failure might lead to memory corruption and crashes)
/Linux-v4.19/Documentation/ide/
Dwarm-plug-howto.txt18 results may be unpredictable and lead to data loss if you're unlucky
/Linux-v4.19/Documentation/devicetree/bindings/media/i2c/
Dadv7343.txt3 The ADV7343 are high speed, digital-to-analog video encoders in a 64-lead LQFP
/Linux-v4.19/drivers/media/pci/ddbridge/
DKconfig41 might lead to I2C errors originating from the bridge in conjunction
/Linux-v4.19/Documentation/hwmon/
Dadm102688 voltage from the power lead rather than on the ground lead.
/Linux-v4.19/drivers/eisa/
DKconfig27 # an X86 may lead to crashes...
/Linux-v4.19/lib/
DKconfig.kasan29 it only includes the address-use-after-scope check that can lead
/Linux-v4.19/scripts/
Dcheckpatch.pl4747 my $lead = $1;
4752 if ($lead !~ /(?:$Operators|\.)\s*$/ &&
5611 my $lead = $fixed[$fixlinenr] =~
5613 $lead = rtrim($1);
5614 $lead = "$lead " if ($lead !~ /^\+$/);
5615 $lead = "${lead}const ";
5616 $fixed[$fixlinenr] =~ s/(^\+\s*(?:static\s+))/$lead/;
6326 my $lead = $1;
/Linux-v4.19/security/tomoyo/
DKconfig48 operations which can lead to the hijacking of the boot sequence are
/Linux-v4.19/Documentation/
Dcpu-load.txt52 will lead to quite erratic information inside ``/proc/stat``::
/Linux-v4.19/scripts/coccinelle/null/
Dbadzero.cocci119 // This rule may lead to inconsistent path problems, if E is defined in two
/Linux-v4.19/Documentation/misc-devices/
Dapds990x.txt29 lead to false interrupt, but that doesn't harm.
/Linux-v4.19/Documentation/core-api/
Dgfp_mask-from-fs-io.rst23 of GFP_NOFS/GFP_NOIO can lead to memory over-reclaim or other memory
Didr.rst61 you may need to pass a restrictive set of GFP flags, which can lead
/Linux-v4.19/Documentation/devicetree/bindings/spi/
Dspi-sprd-adi.txt25 ADI registers will make ADI controller registers chaos to lead incorrect results.
/Linux-v4.19/Documentation/md/
Draid5-ppl.txt7 disks is missing. This can lead to silent data corruption when rebuilding the
/Linux-v4.19/Documentation/driver-api/soundwire/
Derror_handling.rst55 possible in a single segment setup, but this can lead to synchronization
/Linux-v4.19/Documentation/admin-guide/
Dsecurity-bugs.rst50 Fixes for sensitive bugs, such as those that might lead to privilege
/Linux-v4.19/Documentation/locking/
Dlockdep-design.txt81 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-v4.19/Documentation/acpi/
Dvideo_extension.txt92 so this would lead to the same effect as case i) now.
/Linux-v4.19/Documentation/process/
D7.AdvancedTopics.rst79 Excessive use of this capability can lead to other problems, though, beyond
177 All types of review, if they lead to better code going into the kernel, are
/Linux-v4.19/arch/m68k/fpsp040/
Dsetox.S505 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-v4.19/Documentation/i2c/busses/
Di2c-parport155 The project has lead to new libs for the Velleman K8000 and K8005:
/Linux-v4.19/Documentation/media/v4l-drivers/
Dradiotrack.rst41 input is simply an antenna lead, and the output is a power audio signal

12345