| /linux/tools/testing/selftests/powerpc/dexcr/ |
| H A D | dexcr_test.c | 139 "setting aspect on exec wrongly applied to fork"); in dexcr_prctl_aspect_test()
161 "clearing aspect on exec wrongly applied to fork"); in dexcr_prctl_aspect_test()
|
| /linux/Documentation/devicetree/bindings/mfd/ |
| H A D | maxim,max8998.yaml | 89 CHARGER is main battery charger current control, wrongly represented
121 EN32KHz-AP and EN32KHz-CP are 32768 Hz clocks, wrongly represented as
|
| /linux/tools/testing/selftests/bpf/progs/ |
| H A D | stacktrace_map_skip.c | 56 /* it wrongly skipped all the entries and filled zero */ in oncpu()
|
| /linux/drivers/net/wireless/ath/ath9k/ |
| H A D | dfs_debug.h | 29 * @pulses_no_dfs: pulses wrongly reported as DFS
|
| /linux/arch/mips/lib/ |
| H A D | mips-atomic.c | 32 * of the mfc0 might wrongly contain EXL bit.
|
| /linux/include/clocksource/ |
| H A D | hyperv_timer.h | 55 * versions (up to 4.0b) contain a mistake and wrongly claim '-1' in hv_read_tsc_page_tsc()
|
| /linux/drivers/media/rc/keymaps/ |
| H A D | rc-medion-x10-digitainer.c | 80 * this keymap is wrongly used with them (which is quite possible as
|
| /linux/tools/testing/selftests/kvm/aarch64/ |
| H A D | no-vgic-v3.c | 59 "GICv3 wrongly advertised"); in guest_code()
|
| /linux/drivers/iio/pressure/ |
| H A D | sdp500.c | 59 dev_err(data->dev, "Data is received wrongly"); in sdp500_read_raw()
|
| /linux/drivers/cpufreq/ |
| H A D | amd-pstate.h | 37 * calculated wrongly. we take the fixed value as the highest_perf.
|
| /linux/arch/arm64/include/asm/ |
| H A D | arch_gicv3.h | 54 * GIC-CPU interface could wrongly return a valid INTID to the CPU
|
| /linux/drivers/gpu/drm/xe/ |
| H A D | xe_sriov.c | 69 * report SR-IOV capability and the PCI layer may wrongly in xe_sriov_probe_early()
|
| /linux/Documentation/devicetree/bindings/mtd/ |
| H A D | jedec,spi-nor.yaml | 87 flash device is not connected or is wrongly tied to GND (that includes internal
|
| /linux/Documentation/scsi/ |
| H A D | ChangeLog.sym53c8xx_2 | 44 from SCRIPTS :) in the patch method (was wrongly placed in
|
| H A D | ChangeLog.megaraid | 397 were wrongly shared by the ioctl path. This causes a whole IO command
445 driver, do not (wrongly) print information for the "attached" driver
|
| /linux/arch/x86/kernel/ |
| H A D | step.c | 123 * state so we don't wrongly set TIF_FORCED_TF below. in enable_single_step()
|
| /linux/drivers/hid/bpf/progs/ |
| H A D | Thrustmaster__TCA-Yoke-Boeing.bpf.c | 20 * are 2 vendor-defined inputs where the Input type appears to be defined wrongly.
|
| /linux/drivers/watchdog/ |
| H A D | it87_wdt.c | 69 #define IT8726_ID 0x8726 /* the data sheet suggest wrongly 0x8716 */
|
| /linux/arch/arm/mach-omap2/ |
| H A D | dma.c | 90 * Inter Frame DMA buffering issue DMA will wrongly in configure_dma_errata()
|
| /linux/drivers/mtd/parsers/ |
| H A D | ofpart_core.c | 140 …pr_warn("%s: ofpart partition %pOF (%pOF) #size-cells is wrongly set to <0>, assuming <1> for pars… in parse_fixed_partitions()
|
| /linux/arch/loongarch/kernel/ |
| H A D | kprobes.c | 110 * of out-of-line single-step, that result in wrongly single stepping
|
| /linux/drivers/mfd/ |
| H A D | arizona-spi.c | 141 * Some DSDTs wrongly declare the IRQ trigger-type as IRQF_TRIGGER_FALLING in arizona_spi_acpi_probe()
|
| /linux/drivers/parport/ |
| H A D | probe.c | 156 /* Some devices wrongly send LE length, and some send it two in parport_read_device_id()
|
| /linux/drivers/iommu/amd/ |
| H A D | io_pgtable_v2.c | 221 return NULL; /* Wrongly set PSE bit in PTE */ in fetch_pte()
|
| /linux/arch/csky/kernel/probes/ |
| H A D | kprobes.c | 155 * out-of-line single-step, that result in wrongly single stepping
|