Searched refs:lead (Results 1 – 25 of 155) sorted by relevance
1234567
| /Linux-v6.6/drivers/media/pci/ivtv/ |
| D | ivtvfb.c | 379 u16 lead = 0, tail = 0; in ivtvfb_write() local
414 lead = 4 - ((unsigned long)dst & 3); in ivtvfb_write()
415 if (copy_from_user(dst, buf, lead)) in ivtvfb_write()
417 buf += lead; in ivtvfb_write()
418 dst += lead; in ivtvfb_write()
421 if ((count - lead) & 3) in ivtvfb_write()
422 tail = (count - lead) & 3; in ivtvfb_write()
424 dma_size = count - lead - tail; in ivtvfb_write()
426 p + lead + dma_offset, (void __user *)buf, dma_size); in ivtvfb_write()
|
| /Linux-v6.6/Documentation/ABI/obsolete/ |
| D | sysfs-firmware-acpi | 7 the offline failure might lead to memory corruption and crashes)
|
| /Linux-v6.6/arch/arm64/boot/dts/allwinner/ |
| D | sun50i-a64-pinephone-1.1.dts | 17 * 1.0, and the lowest PWM duty cycle that doesn't lead to backlight
|
| D | sun50i-a64-pinephone-1.2.dts | 22 * and the lowest PWM duty cycle that doesn't lead to backlight being off
|
| /Linux-v6.6/Documentation/process/ |
| D | deprecated.rst | 58 risk of them overflowing. This could lead to values wrapping around and a
60 allocations could lead to linear overflows of heap memory and other
116 explicitly ignore overflows, which may lead to unexpected results
137 be NUL terminated. This can lead to various linear read overflows and
160 size limit. This is both inefficient and can lead to linear read overflows
167 Traditionally, using "%p" in format strings would lead to regular address
196 lead to a crash, possible overwriting sensitive contents at the end of the
|
| /Linux-v6.6/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-v6.6/drivers/media/pci/ddbridge/ |
| D | Kconfig | 40 might lead to I2C errors originating from the bridge in conjunction
|
| /Linux-v6.6/Documentation/hwmon/ |
| D | adm1026.rst | 96 voltage from the power lead rather than on the ground lead.
|
| D | stpddc60.rst | 42 could change at the same time as the limit is written to, which will lead to
|
| /Linux-v6.6/Documentation/kbuild/ |
| D | reproducible-builds.rst | 125 Uncommitted changes or different commit ids in git can also lead
129 will be different, which will eventually lead to binary differences.
|
| /Linux-v6.6/drivers/eisa/ |
| D | Kconfig | 48 # an X86 may lead to crashes...
|
| /Linux-v6.6/Documentation/admin-guide/ |
| D | cpu-load.rst | 52 will lead to quite erratic information inside ``/proc/stat``::
|
| /Linux-v6.6/Documentation/core-api/ |
| D | gfp_mask-from-fs-io.rst | 25 of GFP_NOFS/GFP_NOIO can lead to memory over-reclaim or other memory
|
| D | idr.rst | 64 you may need to pass a restrictive set of GFP flags, which can lead
|
| /Linux-v6.6/Documentation/ABI/testing/ |
| D | sysfs-kernel-iommu_groups | 62 system could lead to catastrophic effects (the users might
|
| /Linux-v6.6/Documentation/misc-devices/ |
| D | apds990x.rst | 32 lead to false interrupt, but that doesn't harm.
|
| /Linux-v6.6/scripts/coccinelle/null/ |
| D | badzero.cocci | 120 // This rule may lead to inconsistent path problems, if E is defined in two
|
| /Linux-v6.6/security/tomoyo/ |
| D | Kconfig | 47 operations which can lead to the hijacking of the boot sequence are
|
| /Linux-v6.6/scripts/ |
| D | checkpatch.pl | 5613 my $lead = $1;
5618 if ($lead !~ /(?:$Operators|\.)\s*$/ &&
6556 my $lead = $fixed[$fixlinenr] =~
6558 $lead = rtrim($1);
6559 $lead = "$lead " if ($lead !~ /^\+$/);
6560 $lead = "${lead}const ";
6561 $fixed[$fixlinenr] =~ s/(^\+\s*(?:static\s+))/$lead/;
7348 my $lead = $1;
|
| /Linux-v6.6/Documentation/driver-api/md/ |
| D | raid5-ppl.rst | 9 disks is missing. This can lead to silent data corruption when rebuilding the
|
| /Linux-v6.6/Documentation/driver-api/soundwire/ |
| D | error_handling.rst | 55 possible in a single segment setup, but this can lead to synchronization
|
| /Linux-v6.6/Documentation/admin-guide/hw-vuln/ |
| D | cross-thread-rsb.rst | 55 could lead to information disclosure if the return targets used do not come
|
| /Linux-v6.6/Documentation/ |
| D | atomic_t.txt | 6 can lead to fatal traps on some platforms).
282 Both provide the same functionality, but try_cmpxchg() can lead to more
|
| /Linux-v6.6/Documentation/firmware-guide/acpi/ |
| D | video_extension.rst | 106 so this would lead to the same effect as case i) now.
|
| /Linux-v6.6/Documentation/admin-guide/cgroup-v1/ |
| D | rdma.rst | 31 rdma resources. This can lead to service unavailability.
|
1234567
