Home
last modified time | relevance | path

Searched full:wrongly (Results 1 – 25 of 126) sorted by relevance

123456

/linux-6.12.1/tools/testing/selftests/powerpc/dexcr/
Ddexcr_test.c139 "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-6.12.1/Documentation/devicetree/bindings/mfd/
Dmaxim,max8998.yaml89 CHARGER is main battery charger current control, wrongly represented
121 EN32KHz-AP and EN32KHz-CP are 32768 Hz clocks, wrongly represented as
/linux-6.12.1/tools/testing/selftests/bpf/progs/
Dstacktrace_map_skip.c56 /* it wrongly skipped all the entries and filled zero */ in oncpu()
/linux-6.12.1/drivers/net/wireless/ath/ath9k/
Ddfs_debug.h29 * @pulses_no_dfs: pulses wrongly reported as DFS
/linux-6.12.1/arch/mips/lib/
Dmips-atomic.c32 * of the mfc0 might wrongly contain EXL bit.
/linux-6.12.1/include/clocksource/
Dhyperv_timer.h55 * versions (up to 4.0b) contain a mistake and wrongly claim '-1' in hv_read_tsc_page_tsc()
/linux-6.12.1/drivers/media/rc/keymaps/
Drc-medion-x10-digitainer.c80 * this keymap is wrongly used with them (which is quite possible as
/linux-6.12.1/tools/testing/selftests/kvm/aarch64/
Dno-vgic-v3.c59 "GICv3 wrongly advertised"); in guest_code()
/linux-6.12.1/drivers/iio/pressure/
Dsdp500.c59 dev_err(data->dev, "Data is received wrongly"); in sdp500_read_raw()
/linux-6.12.1/drivers/cpufreq/
Damd-pstate.h37 * calculated wrongly. we take the fixed value as the highest_perf.
/linux-6.12.1/drivers/gpu/drm/xe/
Dxe_sriov.c69 * report SR-IOV capability and the PCI layer may wrongly in xe_sriov_probe_early()
/linux-6.12.1/arch/arm64/include/asm/
Darch_gicv3.h54 * GIC-CPU interface could wrongly return a valid INTID to the CPU
/linux-6.12.1/Documentation/devicetree/bindings/mtd/
Djedec,spi-nor.yaml87 flash device is not connected or is wrongly tied to GND (that includes internal
/linux-6.12.1/fs/reiserfs/
DREADME31 it wrongly, and Richard Stallman agrees with me, when carefully read
/linux-6.12.1/Documentation/scsi/
DChangeLog.sym53c8xx_244 from SCRIPTS :) in the patch method (was wrongly placed in
/linux-6.12.1/arch/x86/kernel/
Dstep.c123 * state so we don't wrongly set TIF_FORCED_TF below. in enable_single_step()
/linux-6.12.1/drivers/hid/bpf/progs/
DThrustmaster__TCA-Yoke-Boeing.bpf.c20 * are 2 vendor-defined inputs where the Input type appears to be defined wrongly.
/linux-6.12.1/drivers/mtd/parsers/
Dofpart_core.c140 …pr_warn("%s: ofpart partition %pOF (%pOF) #size-cells is wrongly set to <0>, assuming <1> for pars… in parse_fixed_partitions()
/linux-6.12.1/arch/arm/mach-omap2/
Ddma.c90 * Inter Frame DMA buffering issue DMA will wrongly in configure_dma_errata()
/linux-6.12.1/drivers/watchdog/
Dit87_wdt.c69 #define IT8726_ID 0x8726 /* the data sheet suggest wrongly 0x8716 */
/linux-6.12.1/drivers/mfd/
Darizona-spi.c141 * Some DSDTs wrongly declare the IRQ trigger-type as IRQF_TRIGGER_FALLING in arizona_spi_acpi_probe()
/linux-6.12.1/arch/loongarch/kernel/
Dkprobes.c110 * of out-of-line single-step, that result in wrongly single stepping
/linux-6.12.1/drivers/iommu/amd/
Dio_pgtable_v2.c221 return NULL; /* Wrongly set PSE bit in PTE */ in fetch_pte()
/linux-6.12.1/drivers/parport/
Dprobe.c156 /* Some devices wrongly send LE length, and some send it two in parport_read_device_id()
/linux-6.12.1/Documentation/dev-tools/
Dkmemleak.rst189 The false positives are objects wrongly reported as being memory leaks

123456