Searched full:wrongly (Results 1 – 25 of 111) sorted by relevance
12345
/Linux-v6.6/tools/testing/selftests/bpf/progs/ |
D | stacktrace_map_skip.c | 56 /* it wrongly skipped all the entries and filled zero */ in oncpu()
|
/Linux-v6.6/drivers/net/wireless/ath/ath9k/ |
D | dfs_debug.h | 29 * @pulses_no_dfs: pulses wrongly reported as DFS
|
/Linux-v6.6/arch/mips/lib/ |
D | mips-atomic.c | 32 * of the mfc0 might wrongly contain EXL bit.
|
/Linux-v6.6/include/clocksource/ |
D | hyperv_timer.h | 55 * 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/ |
D | rc-medion-x10-digitainer.c | 80 * this keymap is wrongly used with them (which is quite possible as
|
/Linux-v6.6/Documentation/devicetree/bindings/mtd/ |
D | jedec,spi-nor.yaml | 84 flash device is not connected or is wrongly tied to GND (that includes internal
|
/Linux-v6.6/arch/arm64/include/asm/ |
D | arch_gicv3.h | 54 * GIC-CPU interface could wrongly return a valid INTID to the CPU
|
/Linux-v6.6/Documentation/scsi/ |
D | ChangeLog.sym53c8xx_2 | 44 from SCRIPTS :) in the patch method (was wrongly placed in
|
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-v6.6/arch/x86/kernel/ |
D | step.c | 121 * state so we don't wrongly set TIF_FORCED_TF below. in enable_single_step()
|
/Linux-v6.6/fs/reiserfs/ |
D | README | 31 it wrongly, and Richard Stallman agrees with me, when carefully read
|
/Linux-v6.6/arch/arm/mach-omap2/ |
D | dma.c | 90 * Inter Frame DMA buffering issue DMA will wrongly in configure_dma_errata()
|
/Linux-v6.6/drivers/watchdog/ |
D | it87_wdt.c | 67 #define IT8726_ID 0x8726 /* the data sheet suggest wrongly 0x8716 */
|
/Linux-v6.6/drivers/mtd/parsers/ |
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-v6.6/arch/loongarch/kernel/ |
D | kprobes.c | 110 * of out-of-line single-step, that result in wrongly single stepping
|
/Linux-v6.6/drivers/mfd/ |
D | arizona-spi.c | 141 * Some DSDTs wrongly declare the IRQ trigger-type as IRQF_TRIGGER_FALLING in arizona_spi_acpi_probe()
|
/Linux-v6.6/drivers/parport/ |
D | probe.c | 156 /* Some devices wrongly send LE length, and some send it two in parport_read_device_id()
|
/Linux-v6.6/Documentation/dev-tools/ |
D | kmemleak.rst | 189 The false positives are objects wrongly reported as being memory leaks
|
/Linux-v6.6/arch/csky/kernel/probes/ |
D | kprobes.c | 155 * out-of-line single-step, that result in wrongly single stepping
|
/Linux-v6.6/samples/seccomp/ |
D | user-trap.c | 142 * we're not wrongly reading someone else's state in order to make in handle_req()
|
/Linux-v6.6/arch/riscv/kernel/probes/ |
D | kprobes.c | 158 * out-of-line single-step, that result in wrongly single stepping
|
/Linux-v6.6/drivers/iommu/amd/ |
D | io_pgtable_v2.c | 225 return NULL; /* Wrongly set PSE bit in PTE */ in fetch_pte()
|
/Linux-v6.6/Documentation/process/ |
D | 6.Followthrough.rst | 102 honestly believe that this decision is going against you wrongly, you can
|
/Linux-v6.6/drivers/media/platform/amphion/ |
D | vpu_cmds.c | 368 * the firmware may enter wfi wrongly. in vpu_session_stop()
|
/Linux-v6.6/drivers/platform/x86/intel/ |
D | vbtn.c | 209 * Since the problem of wrongly reporting SW_TABLET_MODE=1 in combination
|
12345