Home
last modified time | relevance | path

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

12345

/Linux-v6.6/tools/testing/selftests/bpf/progs/
Dstacktrace_map_skip.c56 /* it wrongly skipped all the entries and filled zero */ in oncpu()
/Linux-v6.6/drivers/net/wireless/ath/ath9k/
Ddfs_debug.h29 * @pulses_no_dfs: pulses wrongly reported as DFS
/Linux-v6.6/arch/mips/lib/
Dmips-atomic.c32 * of the mfc0 might wrongly contain EXL bit.
/Linux-v6.6/include/clocksource/
Dhyperv_timer.h55 * versions (up to 4.0b) contain a mistake and wrongly claim '-1' in hv_read_tsc_page_tsc()
/Linux-v6.6/drivers/media/rc/keymaps/
Drc-medion-x10-digitainer.c80 * this keymap is wrongly used with them (which is quite possible as
/Linux-v6.6/Documentation/devicetree/bindings/mtd/
Djedec,spi-nor.yaml84 flash device is not connected or is wrongly tied to GND (that includes internal
/Linux-v6.6/arch/arm64/include/asm/
Darch_gicv3.h54 * GIC-CPU interface could wrongly return a valid INTID to the CPU
/Linux-v6.6/Documentation/scsi/
DChangeLog.sym53c8xx_244 from SCRIPTS :) in the patch method (was wrongly placed in
DChangeLog.megaraid397 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-v6.6/arch/x86/kernel/
Dstep.c121 * state so we don't wrongly set TIF_FORCED_TF below. in enable_single_step()
/Linux-v6.6/fs/reiserfs/
DREADME31 it wrongly, and Richard Stallman agrees with me, when carefully read
/Linux-v6.6/arch/arm/mach-omap2/
Ddma.c90 * Inter Frame DMA buffering issue DMA will wrongly in configure_dma_errata()
/Linux-v6.6/drivers/watchdog/
Dit87_wdt.c67 #define IT8726_ID 0x8726 /* the data sheet suggest wrongly 0x8716 */
/Linux-v6.6/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-v6.6/arch/loongarch/kernel/
Dkprobes.c110 * of out-of-line single-step, that result in wrongly single stepping
/Linux-v6.6/drivers/mfd/
Darizona-spi.c141 * Some DSDTs wrongly declare the IRQ trigger-type as IRQF_TRIGGER_FALLING in arizona_spi_acpi_probe()
/Linux-v6.6/drivers/parport/
Dprobe.c156 /* Some devices wrongly send LE length, and some send it two in parport_read_device_id()
/Linux-v6.6/Documentation/dev-tools/
Dkmemleak.rst189 The false positives are objects wrongly reported as being memory leaks
/Linux-v6.6/arch/csky/kernel/probes/
Dkprobes.c155 * out-of-line single-step, that result in wrongly single stepping
/Linux-v6.6/samples/seccomp/
Duser-trap.c142 * we're not wrongly reading someone else's state in order to make in handle_req()
/Linux-v6.6/arch/riscv/kernel/probes/
Dkprobes.c158 * out-of-line single-step, that result in wrongly single stepping
/Linux-v6.6/drivers/iommu/amd/
Dio_pgtable_v2.c225 return NULL; /* Wrongly set PSE bit in PTE */ in fetch_pte()
/Linux-v6.6/Documentation/process/
D6.Followthrough.rst102 honestly believe that this decision is going against you wrongly, you can
/Linux-v6.6/drivers/media/platform/amphion/
Dvpu_cmds.c368 * the firmware may enter wfi wrongly. in vpu_session_stop()
/Linux-v6.6/drivers/platform/x86/intel/
Dvbtn.c209 * Since the problem of wrongly reporting SW_TABLET_MODE=1 in combination

12345