Home
last modified time | relevance | path

Searched refs:correct (Results 1 – 200 of 330) sorted by relevance

12

/linux-4.1.27/kernel/trace/
Dtrace_branch.c81 entry->correct = val == expect; in probe_likely_condition()
157 field->correct ? " ok " : " MISS ", in trace_branch_print()
226 f->correct++; in ftrace_likely_update()
250 if (p->correct) { in get_incorrect_percent()
252 percent /= p->correct + p->incorrect; in get_incorrect_percent()
276 seq_printf(m, "%8lu %8lu ", p->correct, p->incorrect); in branch_stat_show()
328 if (a->correct > b->correct) in annotated_branch_stat_cmp()
330 if (a->correct < b->correct) in annotated_branch_stat_cmp()
Dtrace_entries.h315 __field( char, correct )
320 __entry->func, __entry->file, __entry->correct),
/linux-4.1.27/Documentation/devicetree/bindings/mtd/
Dnand.txt9 - nand-ecc-strength: integer representing the number of bits to correct
16 of a controller. Together, they say a controller can correct "{strength} bit
Dpxa3xx-nand.txt20 - nand-ecc-strength: number of bits to correct per ECC step
Dhisi504-nand.txt17 - nand-ecc-strength: Number of bits to correct per ECC step.
Dgpmc-nand.txt32 Refer below "How to select correct ECC scheme for your device ?"
95 How to select correct ECC scheme for your device ?
Datmel-nand.txt26 - atmel,pmecc-cap : error correct capability for Programmable Multibit ECC
/linux-4.1.27/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
Daltr_socfpga.txt28 value is the cclk_in_drv(drvsel). The clk-phase is used to enable the correct
/linux-4.1.27/Documentation/networking/
Dxfrm_proc.txt41 e.g. Inbound SAs are correct but SP rule is wrong
44 e.g. Inbound SAs are correct but no SP is found
Ddmfe.txt54 Test and make sure PCI latency is now correct for all cases.
DREADME.sb100068 of "pnpdump" to a file and editing this file to set the correct I/O ports,
85 already in there. Then modify ppp@gi-on to set the correct login name,
147 install the correct versions of the header files in these two directories.
Digbvf.txt17 be activated on kernels that support SR-IOV. SR-IOV requires the correct
Dtlan.txt110 2. Make sure routing is correct.
Dgeneric-hdlc.txt31 Make sure you're using a correct version of sethdlc for your kernel.
Dltpc.txt54 sure you have the correct name for the dummy interface - If it's
Ddecnet.txt84 FTP sites called dn2ethaddr which can compute the correct ethernet
139 - Is the node of the correct type
Dcxgb.txt175 the correct value. This method is provided as a starting point for the
176 correct receive buffer size.
Dbaycom.txt151 leave it to kmod to load the correct driver depending on the application.
Dde4x5.txt74 that the correct bits are compiled (see end of source code).
De1000.txt66 set to auto-negotiate, the board auto-detects the correct duplex. If the
228 partner is set to auto-negotiate, the board will auto-detect the correct
Ddl2k.txt280 Note that RH 7.0 didn't provide correct header files in /usr/include,
/linux-4.1.27/Documentation/
Dbasic_profiling.txt3 correct my mistakes ;-) (mbligh@aracnet.com)
7 Make sure you have the correct System.map / vmlinux referenced!
Dinit.txt17 A) make sure you have the correct root FS type
18 (and root= kernel parameter points to the correct partition),
Ddebugging-modules.txt11 emitted. This debugging message has been removed. The correct way
Dmono.txt50 # Replace /usr/bin/mono with the correct pathname to
Dcrc32.txt115 in the correct multiple to subtract, we can shift a byte at a time.
117 and the correct multiple of the polynomial to subtract is found using
DDMA-attributes.txt50 you are guaranteeing to the platform that you have all the correct and
Dintel_txt.txt207 any other macrocode and its correct operation is critical to the
208 establishment of the DRTM. The process for determining the correct
Dvolatile-considered-harmful.txt9 kernel code is almost never correct; this document describes why.
Datomic_ops.txt36 are guaranteed to be correct reflecting the initialized value if the
57 all threads are guaranteed to be correct reflecting either the value that has
564 It is actually pretty simple to get the memory barrier correct.
Dstable_kernel_rules.txt6 - It must be obviously correct and tested.
Dsvga.txt188 some useless logo using font download and then fail to reset the correct mode.
222 force setting of the correct mode.
Dbus-virt-phys-mapping.txt11 controller the physical address of the buffers, which is correct on x86
/linux-4.1.27/Documentation/video4linux/bttv/
DSound-FAQ12 Sound will work only, if the correct entry is used (for video it often
18 You should verify this is correct. If it isn't, you have to pass the
19 correct board type as insmod argument, "insmod bttv card=2" for
79 What you have to do is figure out the correct values for gpiomask and
DREADME20 to select the correct card type. If you get video but no sound you've
/linux-4.1.27/drivers/staging/ozwpan/
DTODO8 - check USB HCD implementation is complete and correct.
/linux-4.1.27/Documentation/ABI/testing/
Dsysfs-class-rtc-rtc0-device-rtc_calibration7 Every 60 seconds the AB8500 will correct the RTC's value
Dsysfs-devices-platform-docg327 Entering the correct value toggle the lock, and can be observed
Dsysfs-bus-pci-drivers-ehci_hcd44 correct for 2.6.35 (and probably several earlier kernel
Dsysfs-class-mic.txt141 configuration daemon to set the log buffer address. The correct
155 daemon to set the log buffer length address. The correct log
Ddev-kmsg95 necessarily correct, and the stream could be interleaved with
Dsysfs-firmware-dmi11 information in these tables being correct. It equally
/linux-4.1.27/Documentation/devicetree/bindings/sound/
Dsoc-ac97link.txt6 - pinctrl-names: Has to contain following states to setup the correct
Dti,tas5086.txt27 The correct configuration depends on how the power
/linux-4.1.27/Documentation/devicetree/bindings/serial/
Dvt8500-uart.txt15 Aliases may be defined to ensure the correct ordering of the uarts.
Dqcom,msm-uartdm.txt30 Note: Aliases may be defined to ensure the correct ordering of the UARTs.
/linux-4.1.27/drivers/net/ethernet/qlogic/netxen/
Dnetxen_nic_hw.c1498 goto correct; in netxen_nic_pci_mem_write_128M()
1509 goto correct; in netxen_nic_pci_mem_write_128M()
1522 correct: in netxen_nic_pci_mem_write_128M()
1576 goto correct; in netxen_nic_pci_mem_read_128M()
1587 goto correct; in netxen_nic_pci_mem_read_128M()
1600 correct: in netxen_nic_pci_mem_read_128M()
1652 goto correct; in netxen_nic_pci_mem_write_2M()
1658 goto correct; in netxen_nic_pci_mem_write_2M()
1666 correct: in netxen_nic_pci_mem_write_2M()
1720 goto correct; in netxen_nic_pci_mem_read_2M()
[all …]
/linux-4.1.27/drivers/mtd/nand/
Ddavinci_nand.c397 goto correct; in nand_davinci_correct_4bit()
404 correct: in nand_davinci_correct_4bit()
723 info->chip.ecc.correct = nand_davinci_correct_4bit; in nand_davinci_probe()
728 info->chip.ecc.correct = nand_davinci_correct_1bit; in nand_davinci_probe()
Domap2.c1571 stat = chip->ecc.correct(mtd, buf, ecc_code, ecc_calc); in omap_read_page_bch()
1838 nand_chip->ecc.correct = omap_correct_data; in omap_nand_probe()
1861 nand_chip->ecc.correct = nand_bch_correct_data; in omap_nand_probe()
1896 nand_chip->ecc.correct = omap_elm_correct_data; in omap_nand_probe()
1925 nand_chip->ecc.correct = nand_bch_correct_data; in omap_nand_probe()
1960 nand_chip->ecc.correct = omap_elm_correct_data; in omap_nand_probe()
1990 nand_chip->ecc.correct = omap_elm_correct_data; in omap_nand_probe()
Dsharpsl.c173 this->ecc.correct = nand_correct_data; in sharpsl_nand_probe()
Dcs553x_nand.c234 this->ecc.correct = nand_correct_data; in cs553x_init_one()
Dndfc.c164 chip->ecc.correct = nand_correct_data; in ndfc_chip_init()
Dfsmc_nand.c760 stat = chip->ecc.correct(mtd, p, &ecc_code[i], &ecc_calc[i]); in fsmc_read_page_hwecc()
1070 nand->ecc.correct = fsmc_bch8_correct_data; in fsmc_nand_probe()
1075 nand->ecc.correct = nand_correct_data; in fsmc_nand_probe()
Dnand_base.c1201 stat = chip->ecc.correct(mtd, p, &ecc_code[i], &ecc_calc[i]); in nand_read_page_swecc()
1293 stat = chip->ecc.correct(mtd, p, in nand_read_subpage()
1343 stat = chip->ecc.correct(mtd, p, &ecc_code[i], &ecc_calc[i]); in nand_read_page_hwecc()
1395 stat = chip->ecc.correct(mtd, p, &ecc_code[i], NULL); in nand_read_page_hwecc_oob_first()
1440 stat = chip->ecc.correct(mtd, p, oob, NULL); in nand_read_page_syndrome()
3967 if (!ecc->calculate || !ecc->correct || !ecc->hwctl) { in nand_scan_tail()
3994 if ((!ecc->calculate || !ecc->correct || !ecc->hwctl) && in nand_scan_tail()
4029 ecc->correct = nand_correct_data; in nand_scan_tail()
4049 ecc->correct = nand_bch_correct_data; in nand_scan_tail()
Dtmio_nand.c417 nand_chip->ecc.correct = tmio_nand_correct_data; in tmio_probe()
Dlpc32xx_slc.c624 stat = chip->ecc.correct(mtd, buf, oobecc, in lpc32xx_nand_read_page_syndrome()
839 chip->ecc.correct = nand_correct_data; in lpc32xx_nand_probe()
Dtxx9ndfmc.c336 chip->ecc.correct = txx9ndfmc_correct_data; in txx9ndfmc_probe()
Dbf5xx_nand.c800 chip->ecc.correct = bf5xx_nand_correct_data; in bf5xx_nand_probe()
Djz4740_nand.c442 chip->ecc.correct = jz_nand_correct_ecc_rs; in jz_nand_probe()
/linux-4.1.27/Documentation/blackfin/
Dbfin-spi-notes.txt13 the ones using mode 0 or 2 in order to guarantee correct CS toggling behavior.
/linux-4.1.27/Documentation/devicetree/bindings/mfd/
Dpalmas.txt31 ti,mux-padX : set the pad register X (1-2) to the correct muxing for the
/linux-4.1.27/drivers/staging/iio/Documentation/
Dtrigger.txt14 Typically set to THIS_MODULE. Used to ensure correct
Dinkernel.txt42 by calling iio_channel_get(). The correct channel is identified by:
Ddevice.txt30 Set to THIS_MODULE. Used to ensure correct ownership
/linux-4.1.27/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
Dfplsp.doc73 within the package will then enter the correct emulation code routine.
91 Upon return, fp0 holds the correct result. The FPSR is
/linux-4.1.27/Documentation/nfc/
Dnfc-pn544.txt26 33. In HCI mode sent messages are tested for a correct
/linux-4.1.27/Documentation/powerpc/
Dmpc52xx.txt38 mention you/your company in the copyright of some code, I'll correct it
Dbootwrapper.txt39 arch/powerpc/boot/cuboot.*.c. Selection of the correct
103 arch/powerpc/boot/dts/ directory. The Makefile selects the correct device
131 is responsible for selecting the correct wrapper bits for the image type.
/linux-4.1.27/Documentation/devicetree/bindings/x86/
Dce4100.txt35 correct interrupt number, the child node which represents the device has
/linux-4.1.27/Documentation/power/
Ds2ram.txt78 correct date/time! It is therefore advisable to use a program like ntp-date
79 or rdate to reset the correct date/time from an external time source when
Dsuspend-and-cpuhotplug.txt180 and thereby in applying the correct microcode revision to it.
188 to different CPUs, the kernel maintains a copy of the correct microcode
Dswsusp.txt212 A: Doing SUSPEND when you are asked to do FREEZE is always correct,
233 A: That's correct. We need to resume them if we want to write image to
325 (over half of the total system RAM), is it correct that it is likely
Dvideo.txt44 resume. Unfortunately, it is not correct to call the video BIOS at
/linux-4.1.27/Documentation/x86/x86_64/
Dcpu-hotplug-spec19 option (additional_cpus=...), but it is recommended to supply the correct
/linux-4.1.27/scripts/coccinelle/misc/
Dbadty.cocci74 msg="WARNING: Use correct pointer type argument for sizeof"
/linux-4.1.27/Documentation/devicetree/bindings/dma/
Dfsl-imx-dma.txt38 - dma-names: List of string identifiers for the DMA requests. For the correct
Dfsl-imx-sdma.txt12 correct ROM script addresses needed for the driver to work without additional
/linux-4.1.27/Documentation/pcmcia/
Ddevicetable.txt20 upon module initialization, and tell you of the correct hash.
Ddriver-changes.txt96 PCMCIA devices and their correct drivers can now be matched in
/linux-4.1.27/Documentation/locking/
Dlockdep-design.txt20 rolling proof that the state and the dependencies are correct.
144 lock, the lock ordering is fully correct. The validator does not
148 In order to teach the validator about this correct usage model, new
199 [*] assuming that the validator itself is 100% correct, and no other
202 even hardirq-disabled codepaths] are correct and do not interfere
/linux-4.1.27/Documentation/sound/oss/
DESS4 tries to detect the type of ESS chip too. The correct detection of the chip
DREADME.ymfsb61 that specify correct sample frequency. For example, to play your MP3 file
Dbtaudio67 to 448 kHz. Yes, the number of digits is correct. The driver supports
DAudioExcelDSP1618 setup. If the parameters are different, correct it.
/linux-4.1.27/Documentation/ABI/stable/
Dvdso27 that it is correct for their architecture.)
/linux-4.1.27/Documentation/x86/i386/
DIO-APIC.txt100 Generally, it's always possible to find out the correct pirq= settings, just
112 Use smart trial-and-error techniques to find out the correct pirq line ...
/linux-4.1.27/arch/mn10300/lib/
Dmemset.S91 # check we set the correct amount
Dmemcpy.S104 # check we copied the correct amount
Dmemmove.S127 # check we copied the correct amount
/linux-4.1.27/Documentation/arm/SA1100/
Dserial_UART38 must ensure your user space applications make use of the correct device
/linux-4.1.27/Documentation/devicetree/bindings/net/
Damd-xgbe.txt16 correct Rx interrupt watchdog timer value on a DMA channel
Dsti-dwmac.txt19 - resets : phandle pointing to the system reset controller with correct
/linux-4.1.27/scripts/coccinelle/locks/
Dcall_kern.cocci3 //# correct one. It may be desired to unlock the lock, or to not call the
/linux-4.1.27/Documentation/devicetree/bindings/i2c/
Di2c-rk3x.txt18 - on those SoCs an alias with the correct I2C bus ID (bit offset in the GRF)
/linux-4.1.27/Documentation/cpu-freq/
Damd-powernow.txt9 which is the correct driver.
/linux-4.1.27/arch/m68k/fpsp040/
Dsto_res.S7 | correct floating-point destination register. fp0 and fp1
Dutil.S6 | ovf_res: used by overflow to force the correct
187 jmp (%a1) |go to the correct routine
489 | a0 points to correct internal extended precision result.
517 jmp (%a1) |go to the correct routine
Dres_func.S526 | The precision is extended, so the result in etemp is correct.
528 | the correct fp register.
786 bsrl ovf_res |get correct result based on
828 | will be correct for the user's rounding mode and precision. If
1003 | will be correct for the user's rounding mode and precision. If
1246 bsrl unf_sub |get correct result based on
1968 | the 040 uses the dtag to execute the correct microcode.
Dsint.S39 | For the denormalized cases, force the correct result
Dx_store.S50 fmovemx (%a0),%d0 |move to correct register
Dbugfix.S282 | locations on the stack. The correct destination register is in
408 | locations on the stack. The correct destination register is in
Dgen_except.S252 | to make sure that WBTEMP is correct.
345 | Use a1 as pointer into new frame. a6 is not correct if an unimp or
Dx_operr.S306 | with correct data written to the destination.
Ddecbin.S442 asrl #1,%d0 |write correct PTENxx table
Dskeleton.S91 | return was inex, rather than the correct exception. The snan, ovfl,
/linux-4.1.27/Documentation/sound/alsa/soc/
Dclocking.txt13 (e.g. crystal, PLL, CPU clock) and is responsible for producing the correct
Doverview.txt46 codec up/down in the correct sequence (including using digital mute). ASoC
/linux-4.1.27/arch/x86/kernel/
Dhead_64.S293 pushq $__KERNEL_CS # set correct cs
309 pushq $__KERNEL_CS # set correct cs
/linux-4.1.27/arch/arm/nwfpe/
Dfpmodule.inl29 depend on the PC being correct, as they use PC+8 in their
/linux-4.1.27/Documentation/power/regulator/
Dmachine.txt13 The drivers for consumers A & B must be mapped to the correct regulator in
Dconsumer.txt16 then finds the correct regulator by consulting a machine specific lookup table.
73 correct card voltage, etc.
/linux-4.1.27/sound/soc/blackfin/
DKconfig168 Set the correct GPIO for RESET the sound chip.
205 Set the correct SPORT for sound chip.
/linux-4.1.27/Documentation/video4linux/cx2341x/
Dfw-decoder-api.txt82 has to be set to the correct value in order to keep the timing correct.
Dfw-memory.txt7 registers, this information may not be correct and is certainly not complete, and
/linux-4.1.27/Documentation/netlabel/
Dlsm_interface.txt21 NetLabel subsystem converts the security attributes to and from the correct
/linux-4.1.27/arch/alpha/lib/
Dmemchr.S135 mov $1, $4 # e0 : move prefetched value to correct reg
Dev6-memchr.S150 mov $1, $4 # E : L U L U : move prefetched value to correct reg
/linux-4.1.27/fs/befs/
DChangeLog7 * Fixed module makefile problem. It was not compiling all the correct
76 * Made functions in endian.h to do the correct byteswapping, no matter
219 correct (see TODO list). But it isn't 1.0 yet. I think 0.4 gives me some
233 So it does i/o in much larger chunks. It is the correct linux way. It
/linux-4.1.27/arch/mips/include/asm/mach-cavium-octeon/
Dkernel-entry-init.h72 # Zero all of CVMSEG to make sure parity is correct
/linux-4.1.27/Documentation/devicetree/bindings/arm/
Darch_timer.txt22 CNTFRQ on all CPUs to a uniform correct value. Use of this property is
Dvexpress.txt12 maps"), care must be taken to include the correct one.
/linux-4.1.27/kernel/time/
Dtimeconst.bc29 a shift value will be correct in the signed integer range and off
/linux-4.1.27/Documentation/scsi/
Dscsi.txt22 will enforce the correct ordering of loading and unloading modules in
Dst.txt494 correct. The user can request using direct spacing to EOD by setting
499 may not be correct after the file is closed (correct position may
500 require backspacing over more than one record). The correct position
519 waiting. If you have the current System.map in the correct place (in
Dscsi-changer.txt155 find the correct values as they are not covered by the SCSI-2
DChangeLog.1992-1997168 Is this correct???
575 information for a valid command. Pass correct size down to
827 print correct function name.
1018 * sr.c: Print correct device number.
1112 * st.c: Print correct number for device.
1696 correct. Same bugfix as was in sd.c. Increase read-ahead a la
/linux-4.1.27/arch/m68k/ifpsp060/src/
Dpfpsp.S967 # special case will simply exit gracefully with the correct result.
1394 # here, we insert the correct fsave status value into the fsave frame for the
1972 # here, we insert the correct fsave status value into the fsave frame for the
2398 # - None (correct result has been stored as appropriate) #
3582 # hardware doesn't store the correct result to the destination FP #
3585 # correct register before calling _real_inex(). #
3848 # _dcalc_ea(): calc correct <ea> from <ea> stacked on exception #
3863 # two packed instructions is correct with the exception of... #
3923 mov.l EXC_EA(%a6),%a0 # stacked <ea> is correct
3929 sub.l &0x8,%a0 # correct <ea>
[all …]
Dilsp.S92 # the event occurred even though it may not point to the correct place. #
325 # will yield verifiably correct results..
418 # first quotient digit now correct. store digit and shift the
649 eori.b &0x1,%d5 # calculate correct sign
Dfpsp.S968 # special case will simply exit gracefully with the correct result.
1395 # here, we insert the correct fsave status value into the fsave frame for the
1973 # here, we insert the correct fsave status value into the fsave frame for the
2399 # - None (correct result has been stored as appropriate) #
3583 # hardware doesn't store the correct result to the destination FP #
3586 # correct register before calling _real_inex(). #
3835 # correct emulation code (for "FPU unimplemented"). #
8428 # if these 2 lines weren't here, the correct answer would be returned
11658 # multiply using extended precision and the correct rounding mode. the result
11757 # no, it didn't overflow; we have correct result
[all …]
/linux-4.1.27/drivers/net/wireless/b43legacy/
DKconfig14 layer will automatically load the correct version for your device.
/linux-4.1.27/Documentation/EDID/
DHOWTO.txt56 displays the correct CRC which must then be inserted into the source
/linux-4.1.27/Documentation/spi/
Dpxa2xx118 to determine the correct value. An SSP configured for byte-wide transfers would
123 trailing bytes in the SSP receiver fifo. The correct value for this field is
/linux-4.1.27/Documentation/vm/
Dpage_migration74 how to allocate the correct new page given the old page.
100 accesses to the new page will discover a page with the correct settings.
/linux-4.1.27/Documentation/driver-model/
Ddesign-patterns.txt62 This way you always get a pointer back to the correct instance of foo in
/linux-4.1.27/Documentation/sound/alsa/
Demu10k1-jack.txt22 select the correct device for JACK to use. Actually, for qjackctl users it's
DAudiophile-Usb.txt19 1 - Audiophile USB Specs and correct usage
248 correct device_setup parameter and then (and only then) turn on the device again.
360 In order to ensure a correct initialization of the device, the driver
DREADME.maya4480 *I hope this is the correct way to do things.*
/linux-4.1.27/include/linux/
Dcompiler.h89 unsigned long correct; member
/linux-4.1.27/Documentation/devicetree/
Doverlay-notes.txt100 of_overlay_destroy_all() which will remove every single one in the correct
/linux-4.1.27/Documentation/video4linux/
Duvcvideo.txt71 and set the buffer size to the correct value. Similarly, to find out whether
204 Applications must set the 'size' field to the correct length for the
Domap3isp.txt79 (When using parallel interface one must pay account to correct configuration
80 of the VS signal polarity. This is automatically correct when using the serial
/linux-4.1.27/Documentation/fb/
Dintel810.txt99 Recommendation: check monitor manual for correct values
108 Recommendation: check monitor manual for correct values
Duvesafb.txt133 the correct values for maxhf, maxvf and maxclk for your hardware.
/linux-4.1.27/Documentation/hwmon/
Dabituguru29 revison 1 motherboards the correct use of this param is:
Dsmsc47m19245 is correct, i.e. that the BIOS has updated the configuration if
Dcoretemp49 If these heuristics don't work for you, you can pass the correct TjMax value
Dadm1021107 only temp2 will be correct and temp1 will have to be ignored.
Dds162178 instantiation is required for correct device identification and functionality
Df71805f83 (2) Obviously not correct, swapping R1 and R2 would make more sense.
/linux-4.1.27/Documentation/filesystems/nfs/
Didmapper.txt71 determines the correct function to call by looking at the first part of the
DExporting138 to find potential names, and matches inode numbers to find the correct
/linux-4.1.27/Documentation/isdn/
DREADME.sc28 1.3 How do I setup my system with the correct software to use
92 1.3 How do I setup my system with the correct software to use
99 versions. Please see your distribution vendor for the correct
/linux-4.1.27/Documentation/devicetree/bindings/pinctrl/
Dfsl,imx-pinctrl.txt94 User should refer to each SoC spec to set the correct value.
/linux-4.1.27/Documentation/dvb/
Dbt8xx.txt84 reason. The cards do not have correct PCI subsystem ID. But we can force
/linux-4.1.27/Documentation/devicetree/bindings/pci/
Dralink,rt3883-pci.txt79 are used to refer to the correct bus number and device number.
Dmvebu-pci.txt61 are used to refer to the correct bus number and device number.
/linux-4.1.27/Documentation/networking/caif/
DREADME106 E.g. host and modem wiring is not correct you will typically see
DLinux-CAIF.txt113 into CAIF Frames with correct length.
/linux-4.1.27/arch/unicore32/
DKconfig163 correct operation of some network protocols. With an IP-only
/linux-4.1.27/arch/m68k/math-emu/
Dfp_entry.S81 | user space, we correct stackpointer and send a SIGSEGV to
/linux-4.1.27/arch/xtensa/lib/
Dmemcopy.S270 add a3, a3, a11 # readjust a3 with correct misalignment
545 add a3, a3, a11 # readjust a3 with correct misalignment
Dusercopy.S268 add a3, a3, a10 # readjust a3 with correct misalignment
/linux-4.1.27/Documentation/filesystems/
Dvfat.txt86 correct, by this option you can avoid scanning disk.
120 option still does not provide correct time stamps in all
222 Windows 95. I don't guarantee that any of the following is correct,
Dxfs-self-describing-metadata.txt47 not detected by automated verification checks) but are not correct. Finding and
93 metadata block can be verified as being in the correct place without needing to
97 written to the "correct block" of the wrong filesystem. Hence location
/linux-4.1.27/arch/powerpc/boot/dts/
Dmpc5125twr.dts234 // correct pinmux config and fix USB3320 ulpi dependency
/linux-4.1.27/drivers/net/appletalk/
DKconfig29 even politically correct people are allowed to say Y here.
/linux-4.1.27/include/sound/
Dwavefront.h35 still have the same (correct) size.
/linux-4.1.27/arch/arm/plat-omap/
DKconfig80 This is useful if you want to find out the correct values of the
/linux-4.1.27/Documentation/devicetree/bindings/bus/
Dti-gpmc.txt33 As this will change in the future, filling correct
/linux-4.1.27/Documentation/i2c/busses/
Di2c-piix459 correct address for this module, you could get in big trouble (read:
/linux-4.1.27/Documentation/trace/
Dtracepoints.txt104 to make sure typing is correct. Verification of probe type correctness
/linux-4.1.27/Documentation/serial/
Dmoxa-smartio200 3.4.1 Create tty device with correct major number
361 e. make install /* copy boot image to correct position */
363 correct position.
/linux-4.1.27/Documentation/i2c/
Dfault-codes76 may verify the device returns *correct* responses, and
Dupgrading-clients208 And finally ensure that we have the correct ID table for the i2c-core
/linux-4.1.27/drivers/net/wireless/b43/
DKconfig22 layer will automatically load the correct version for your device.
/linux-4.1.27/Documentation/device-mapper/
Dswitch.txt39 sending data directly to the correct member.
Dlog-writes.txt117 <verify md5sum's are correct>
/linux-4.1.27/Documentation/devicetree/bindings/powerpc/4xx/
Demac.txt8 correct clock-frequency property.
/linux-4.1.27/arch/xtensa/
DKconfig450 the correct address. Wrong address here may lead to hardware lockup.
459 guide for your board for the correct interface width.
/linux-4.1.27/arch/unicore32/kernel/
Dentry.S179 @ r2 - lr_<exception>, already fixed up for correct return/restart
206 @ r2 - lr_<exception>, already fixed up for correct return/restart
/linux-4.1.27/drivers/s390/char/
DKconfig110 The Component ID for Call Home is used to identify the correct
/linux-4.1.27/arch/cris/boot/rescue/
Dhead_v10.S173 ;; check for correct magic
/linux-4.1.27/Documentation/x86/
Dearlyprintk.txt88 specify the correct EHCI debug controller number. The ordering
/linux-4.1.27/Documentation/arm/
DInterrupts149 parent IRQ via the correct chip specific function. For instance, if
DREADME148 could be a bit of a problem! Suggestions on the correct way to do this
/linux-4.1.27/arch/sh/mm/
DKconfig60 already have a defconfig. Changing it from the known correct
/linux-4.1.27/Documentation/gpio/
Dsysfs.txt117 the correct GPIO number to use for a given signal.
/linux-4.1.27/arch/x86/
DKconfig.cpu112 flags optimized for the chip, uses the correct cache line size, and
240 Select this for a VIA C7. Selecting this uses the correct cache
/linux-4.1.27/arch/arm/mach-davinci/
DKconfig235 This is useful if you want to find out the correct values of the
/linux-4.1.27/Documentation/laptops/
Dasus-laptop.txt244 reports, especially if they add to or correct the compatibility table.
/linux-4.1.27/include/linux/mtd/
Dnand.h500 int (*correct)(struct mtd_info *mtd, uint8_t *dat, uint8_t *read_ecc, member
/linux-4.1.27/Documentation/filesystems/cifs/
DCHANGES118 lanman and plain text though). Fix writes to be at correct offset when
589 that do not report the correct mode (do not support the
620 unitialized. Reset search to restart at correct file when kernel routine
990 files now return the correct number of links on fstat as they are repeatedly linked and unlinked.
1037 1) Fixed lockrange to be correct (it was one byte too short)
1043 in most cases. Eventually will offer optional ability to query server for the correct perms.
/linux-4.1.27/fs/
DKconfig.binfmt160 will automatically feed it to the correct interpreter.
/linux-4.1.27/drivers/mtd/
Dnftlmount.c163 device is already correct. in find_boot_record()
/linux-4.1.27/Documentation/watchdog/
Dwatchdog-api.txt158 return. [FIXME -- Is this correct?]
/linux-4.1.27/Documentation/blockdev/
Dparide.txt100 correct device.
385 (using the correct driver for the type of device you have, of course).
/linux-4.1.27/fs/affs/
DChanges279 - Tried to make all types 'correct' and consistent.
/linux-4.1.27/Documentation/timers/
Dhrtimers.txt47 recascaded because the expected correct event arrives in time so they

12