Home
last modified time | relevance | path

Searched refs:correct (Results 1 – 25 of 465) sorted by relevance

12345678910>>...19

/linux-6.1.9/kernel/trace/
Dtrace_branch.c83 entry->correct = val == expect; in probe_likely_condition()
148 field->correct ? " ok " : " MISS ", in trace_branch_print()
225 f->data.correct++; in ftrace_likely_update()
251 if (p->correct) { in get_incorrect_percent()
253 percent /= p->correct + p->incorrect; in get_incorrect_percent()
292 seq_printf(m, "%8lu %8lu ", p->correct, p->incorrect); in branch_stat_show_normal()
312 p->data.correct, p->constant, l, p->data.incorrect); in annotate_branch_stat_show()
360 if (a->correct > b->correct) in annotated_branch_stat_cmp()
362 if (a->correct < b->correct) in annotated_branch_stat_cmp()
Dtrace_entries.h304 __field( char, correct )
310 __entry->func, __entry->file, __entry->correct,
/linux-6.1.9/Documentation/devicetree/bindings/clock/
Dsilabs,si570.txt20 The correct frequency for the part used has to be provided in
21 order to generate the correct output frequencies. For more
/linux-6.1.9/Documentation/networking/
Dxfrm_proc.rst58 e.g. Inbound SAs are correct but SP rule is wrong
62 e.g. Inbound SAs are correct but no SP is found
/linux-6.1.9/Documentation/driver-api/media/drivers/
Dbttv-devel.rst16 Sound will work only, if the correct entry is used (for video it often
22 You should verify this is correct. If it isn't, you have to pass the
23 correct board type as insmod argument, ``insmod bttv card=2`` for
85 What you have to do is figure out the correct values for gpiomask and
/linux-6.1.9/arch/arm64/boot/dts/qcom/
Dmsm8992-lg-bullhead-rev-10.dts12 /* required for bootloader to select correct board */
Dmsm8992-lg-bullhead-rev-101.dts12 /* required for bootloader to select correct board */
Dmsm8998-oneplus-dumpling.dts14 /* Required for bootloader to select correct board */
Dmsm8998-oneplus-cheeseburger.dts15 /* Required for bootloader to select correct board */
Dmsm8994-huawei-angler-rev-101.dts18 /* required for bootloader to select correct board */
/linux-6.1.9/Documentation/admin-guide/
Dinit.rst12 2) **init binary doesn't exist on rootfs**: Make sure you have the correct
13 root FS type (and ``root=`` kernel parameter points to the correct
/linux-6.1.9/Documentation/devicetree/bindings/sound/
Dsoc-ac97link.txt6 - pinctrl-names: Has to contain following states to setup the correct
/linux-6.1.9/tools/testing/memblock/
DTODO16 3. Add tests for memblock_alloc_node() to check if the correct NUMA node is set
/linux-6.1.9/Documentation/ABI/testing/
Dsysfs-class-rtc-rtc0-device-rtc_calibration8 Every 60 seconds the AB8500 will correct the RTC's value
/linux-6.1.9/Documentation/core-api/
Ddebug-objects.rst77 structure if provided by the caller. The fixup function can correct the
100 structure if provided by the caller. The fixup function can correct the
124 structure if provided by the caller. The fixup function can correct the
164 provided by the caller. The fixup function can correct the problem
180 fixup function can correct the problem before the real free of the
196 fixup function can correct the problem by calling debug_object_init
/linux-6.1.9/drivers/staging/olpc_dcon/
DTODO8 internals, but isn't properly integrated, is not the correct solution.
/linux-6.1.9/drivers/mtd/nand/raw/ingenic/
Dingenic_ecc.h68 int (*correct)(struct ingenic_ecc *ecc, member
/linux-6.1.9/Documentation/devicetree/bindings/serial/
Dvt8500-uart.txt15 Aliases may be defined to ensure the correct ordering of the uarts.
/linux-6.1.9/Documentation/w1/slaves/
Dw1_ds2438.rst44 from the slave device. If it is correct, the 8 bytes page data are passed
52 from the slave device. If it is correct, the 8 bytes page data are passed
/linux-6.1.9/Documentation/devicetree/bindings/media/
Dhix5hd2-ir.txt16 Provide correct clocks instead.
/linux-6.1.9/drivers/net/ethernet/qlogic/netxen/
Dnetxen_nic_hw.c1457 goto correct; in netxen_nic_pci_mem_write_128M()
1468 goto correct; in netxen_nic_pci_mem_write_128M()
1481 correct: in netxen_nic_pci_mem_write_128M()
1535 goto correct; in netxen_nic_pci_mem_read_128M()
1546 goto correct; in netxen_nic_pci_mem_read_128M()
1559 correct: in netxen_nic_pci_mem_read_128M()
1611 goto correct; in netxen_nic_pci_mem_write_2M()
1617 goto correct; in netxen_nic_pci_mem_write_2M()
1625 correct: in netxen_nic_pci_mem_write_2M()
1679 goto correct; in netxen_nic_pci_mem_read_2M()
[all …]
/linux-6.1.9/drivers/mtd/nand/raw/
Ddavinci_nand.c334 goto correct; in nand_davinci_correct_4bit()
341 correct: in nand_davinci_correct_4bit()
561 chip->ecc.correct = nand_davinci_correct_4bit; in davinci_nand_attach_chip()
590 chip->ecc.correct = nand_davinci_correct_1bit; in davinci_nand_attach_chip()
/linux-6.1.9/Documentation/devicetree/bindings/display/panel/
Dasus,z00t-tm5p5-nt35596.yaml15 actually getting the correct model number,
/linux-6.1.9/arch/m68k/ifpsp060/
Dilsp.doc72 within the package will then enter the correct emulation code routine.
110 The library routines also return the correct condition code
133 point to the correct instruction, the user will at least be able
/linux-6.1.9/Documentation/devicetree/bindings/timer/
Darm,arch_timer.yaml63 CNTFRQ on all CPUs to a uniform correct value. Use of this property is
88 return a value 32 beyond the correct value. This also affects writes to

12345678910>>...19