/linux-4.4.14/Documentation/dvb/ |
D | get_dvb_firmware | 73 verify("$tmpdir/software/OEM/HE/App/boot/SC_MAIN.MC", $hash); 93 verify("$tmpdir/ZEnglish/sc_main.mc", $hash); 111 verify("$tmpdir/fwtmp", $hash); 129 verify("$tmpdir/fwtmp", $hash); 147 verify("$tmpdir/fwtmp", $hash); 162 verify($sourcefile, $hash); 179 verify("$tmpdir/software/OEM/STB/App/Boot/STB_PC_T.bin", $hash); 196 verify("$tmpdir/software/OEM/STB/App/Boot/STB_PC_X.bin", $hash); 213 verify("$tmpdir/software/OEM/STB/App/Boot/STB_PC_S.bin", $hash); 229 verify("$tmpdir/fw1part1-1","5e0909858fdf0b5b09ad48b9fe622e70"); [all …]
|
/linux-4.4.14/tools/testing/selftests/sysctl/ |
D | common_tests | 17 verify() 33 if ! verify "${TEST_FILE}"; then 41 if verify "${TARGET}"; then 50 if ! verify "${TARGET}"; then 59 if verify "${TARGET}"; then 73 if ! verify "${TARGET}"; then 83 if ! verify "${TARGET}"; then 93 if verify "${TARGET}"; then 104 if verify "${TARGET}"; then
|
D | run_stringtests | 16 if ! verify "${TARGET}"; then 26 if verify "${TARGET}"; then
|
/linux-4.4.14/arch/sparc/boot/ |
D | install.sh | 20 verify () { function 31 verify "$2" 32 verify "$3"
|
/linux-4.4.14/arch/m68k/ |
D | install.sh | 20 verify () { function 31 verify "$2" 32 verify "$3"
|
/linux-4.4.14/arch/nios2/boot/ |
D | install.sh | 20 verify () { function 31 verify "$2" 32 verify "$3"
|
/linux-4.4.14/arch/parisc/ |
D | install.sh | 22 verify () { function 34 verify "$2" 35 verify "$3"
|
/linux-4.4.14/arch/blackfin/boot/ |
D | install.sh | 23 verify () { function 34 verify "$2" 35 verify "$3"
|
/linux-4.4.14/arch/arm/boot/ |
D | install.sh | 23 verify () { function 34 verify "$2" 35 verify "$3"
|
/linux-4.4.14/arch/x86/boot/ |
D | install.sh | 20 verify () { function 31 verify "$2" 32 verify "$3"
|
/linux-4.4.14/drivers/mtd/tests/ |
D | mtd_nandecctest.c | 29 int (*verify)(void *, void *, void *, const size_t); member 197 .verify = no_bit_error_verify, 202 .verify = single_bit_error_correct, 207 .verify = single_bit_error_correct, 212 .verify = double_bit_error_detect, 217 .verify = double_bit_error_detect, 222 .verify = double_bit_error_detect, 267 err = nand_ecc_test[i].verify(error_data, error_ecc, in nand_ecc_test_run()
|
/linux-4.4.14/drivers/net/ethernet/mellanox/mlx4/ |
D | cmd.c | 1068 .verify = NULL, 1077 .verify = NULL, 1086 .verify = NULL, 1095 .verify = NULL, 1104 .verify = NULL, 1113 .verify = NULL, 1122 .verify = NULL, 1131 .verify = NULL, 1140 .verify = NULL, 1149 .verify = NULL, [all …]
|
D | mlx4.h | 202 int (*verify)(struct mlx4_dev *dev, int slave, struct mlx4_vhcr *vhcr, member
|
/linux-4.4.14/drivers/net/ethernet/microchip/ |
D | Kconfig | 30 bool "Enable write verify" 33 Enable the verify after the buffer write useful for debugging purpose.
|
/linux-4.4.14/include/crypto/ |
D | akcipher.h | 94 int (*verify)(struct akcipher_request *req); member 342 return alg->verify(req); in crypto_akcipher_verify()
|
/linux-4.4.14/drivers/scsi/cxlflash/ |
D | superpipe.c | 1703 struct dk_cxlflash_verify *verify) in process_sense() argument 1713 rc = scsi_normalize_sense((const u8 *)&verify->sense_data, in process_sense() 1768 struct dk_cxlflash_verify *verify) in cxlflash_disk_verify() argument 1777 res_hndl_t rhndl = verify->rsrc_handle; in cxlflash_disk_verify() 1778 u64 ctxid = DECODE_CTXID(verify->context_id), in cxlflash_disk_verify() 1779 rctxid = verify->context_id; in cxlflash_disk_verify() 1783 "flags=%016llX\n", __func__, ctxid, verify->rsrc_handle, in cxlflash_disk_verify() 1784 verify->hint, verify->hdr.flags); in cxlflash_disk_verify() 1805 if (verify->hint & DK_CXLFLASH_VERIFY_HINT_SENSE) { in cxlflash_disk_verify() 1811 rc = process_sense(sdev, verify); in cxlflash_disk_verify() [all …]
|
/linux-4.4.14/drivers/md/bcache/ |
D | sysfs.c | 99 rw_attribute(verify); 123 var_printf(verify, "%i"); in SHOW() 203 d_strtoul(verify); in STORE() 565 sysfs_printf(verify, "%i", c->verify); in SHOW() 649 sysfs_strtoul(verify, c->verify); in STORE()
|
D | bcache.h | 353 unsigned verify:1; member 657 unsigned verify:1; member
|
D | request.c | 34 static bool verify(struct cached_dev *dc, struct bio *bio) in verify() function 36 return dc->verify; in verify() 754 if (verify(dc, &s->bio.bio) && s->recoverable && !s->read_dirty_data) in cached_dev_read_done() 779 else if (s->iop.bio || verify(dc, &s->bio.bio)) in cached_dev_read_done_bh()
|
D | debug.c | 36 if (!b->c->verify || !b->c->verify_ondisk) in bch_btree_verify()
|
/linux-4.4.14/Documentation/fmc/ |
D | fmc-trivial.txt | 5 interrupt handler. I used it to verify the basic mechanism of the FMC
|
D | fmc-fakedev.txt | 15 You can also use this device to verify the match algorithms, by asking
|
/linux-4.4.14/fs/nfsd/ |
D | nfs4proc.c | 1101 struct nfsd4_verify *verify) in _nfsd4_verify() argument 1111 status = check_attr_support(rqstp, cstate, verify->ve_bmval, NULL); in _nfsd4_verify() 1115 if ((verify->ve_bmval[0] & FATTR4_WORD0_RDATTR_ERROR) in _nfsd4_verify() 1116 || (verify->ve_bmval[1] & NFSD_WRITEONLY_ATTRS_WORD1)) in _nfsd4_verify() 1118 if (verify->ve_attrlen & 3) in _nfsd4_verify() 1124 count = 4 + (verify->ve_attrlen >> 2); in _nfsd4_verify() 1133 verify->ve_bmval, in _nfsd4_verify() 1147 if (ntohl(*p++) != verify->ve_attrlen) in _nfsd4_verify() 1149 if (!memcmp(p, verify->ve_attrval, verify->ve_attrlen)) in _nfsd4_verify() 1159 struct nfsd4_verify *verify) in nfsd4_nverify() argument [all …]
|
D | xdr4.h | 536 struct nfsd4_verify verify; member
|
D | nfs4xdr.c | 1189 nfsd4_decode_verify(struct nfsd4_compoundargs *argp, struct nfsd4_verify *verify) in nfsd4_decode_verify() argument 1193 if ((status = nfsd4_decode_bitmap(argp, verify->ve_bmval))) in nfsd4_decode_verify() 1200 verify->ve_attrlen = be32_to_cpup(p++); in nfsd4_decode_verify() 1201 READ_BUF(verify->ve_attrlen); in nfsd4_decode_verify() 1202 SAVEMEM(verify->ve_attrval, verify->ve_attrlen); in nfsd4_decode_verify()
|
/linux-4.4.14/fs/ext4/ |
D | balloc.c | 435 goto verify; in ext4_read_block_bitmap_nowait() 440 goto verify; in ext4_read_block_bitmap_nowait() 454 goto verify; in ext4_read_block_bitmap_nowait() 464 goto verify; in ext4_read_block_bitmap_nowait() 475 verify: in ext4_read_block_bitmap_nowait()
|
D | ialloc.c | 177 goto verify; in ext4_read_inode_bitmap() 182 goto verify; in ext4_read_inode_bitmap() 209 goto verify; in ext4_read_inode_bitmap() 227 verify: in ext4_read_inode_bitmap()
|
/linux-4.4.14/drivers/cpufreq/ |
D | dbx500-cpufreq.c | 38 .verify = cpufreq_generic_frequency_table_verify,
|
D | unicore2-cpufreq.c | 68 .verify = ucv2_verify_speed,
|
D | sc520_freq.c | 93 .verify = cpufreq_generic_frequency_table_verify,
|
D | cris-artpec3-cpufreq.c | 57 .verify = cpufreq_generic_frequency_table_verify,
|
D | cris-etraxfs-cpufreq.c | 57 .verify = cpufreq_generic_frequency_table_verify,
|
D | sa1100-cpufreq.c | 205 .verify = cpufreq_generic_frequency_table_verify,
|
D | elanfreq.c | 197 .verify = cpufreq_generic_frequency_table_verify,
|
D | ppc_cbe_cpufreq.c | 142 .verify = cpufreq_generic_frequency_table_verify,
|
D | at32ap-cpufreq.c | 117 .verify = cpufreq_generic_frequency_table_verify,
|
D | sfi-cpufreq.c | 81 .verify = cpufreq_generic_frequency_table_verify,
|
D | loongson2_cpufreq.c | 114 .verify = cpufreq_generic_frequency_table_verify,
|
D | maple-cpufreq.c | 151 .verify = cpufreq_generic_frequency_table_verify,
|
D | tegra20-cpufreq.c | 169 .verify = cpufreq_generic_frequency_table_verify,
|
D | blackfin-cpufreq.c | 194 .verify = cpufreq_generic_frequency_table_verify,
|
D | kirkwood-cpufreq.c | 98 .verify = cpufreq_generic_frequency_table_verify,
|
D | s3c64xx-cpufreq.c | 216 .verify = cpufreq_generic_frequency_table_verify,
|
D | sh-cpufreq.c | 155 .verify = sh_cpufreq_verify,
|
D | omap-cpufreq.c | 153 .verify = cpufreq_generic_frequency_table_verify,
|
D | cppc_cpufreq.c | 127 .verify = cppc_verify_policy,
|
D | davinci-cpufreq.c | 124 .verify = davinci_verify_speed,
|
D | spear-cpufreq.c | 163 .verify = cpufreq_generic_frequency_table_verify,
|
D | p4-clockmod.c | 237 .verify = cpufreq_generic_frequency_table_verify,
|
D | sparc-us3-cpufreq.c | 195 driver->verify = cpufreq_generic_frequency_table_verify; in us3_freq_init()
|
D | pasemi-cpufreq.c | 264 .verify = cpufreq_generic_frequency_table_verify,
|
D | pxa3xx-cpufreq.c | 205 .verify = cpufreq_generic_frequency_table_verify,
|
D | integrator-cpufreq.c | 192 .verify = integrator_verify_policy,
|
D | speedstep-ich.c | 311 .verify = cpufreq_generic_frequency_table_verify,
|
D | powernow-k6.c | 249 .verify = cpufreq_generic_frequency_table_verify,
|
D | longrun.c | 282 .verify = longrun_verify_policy,
|
D | speedstep-smi.c | 292 .verify = cpufreq_generic_frequency_table_verify,
|
D | ls1x-cpufreq.c | 122 .verify = cpufreq_generic_frequency_table_verify,
|
D | sa1110-cpufreq.c | 316 .verify = cpufreq_generic_frequency_table_verify,
|
D | cpufreq-nforce2.c | 374 .verify = nforce2_verify,
|
D | sparc-us2e-cpufreq.c | 336 driver->verify = cpufreq_generic_frequency_table_verify; in us2e_freq_init()
|
D | ia64-acpi-cpufreq.c | 345 .verify = cpufreq_generic_frequency_table_verify,
|
D | pxa2xx-cpufreq.c | 427 .verify = cpufreq_generic_frequency_table_verify,
|
D | gx-suspmod.c | 442 .verify = cpufreq_gx_verify,
|
D | qoriq-cpufreq.c | 329 .verify = cpufreq_generic_frequency_table_verify,
|
D | s3c2416-cpufreq.c | 479 .verify = cpufreq_generic_frequency_table_verify,
|
D | e_powersaver.c | 391 .verify = cpufreq_generic_frequency_table_verify,
|
D | imx6q-cpufreq.c | 171 .verify = cpufreq_generic_frequency_table_verify,
|
D | speedstep-centrino.c | 510 .verify = cpufreq_generic_frequency_table_verify,
|
D | pmac32-cpufreq.c | 437 .verify = cpufreq_generic_frequency_table_verify,
|
D | cpufreq-dt.c | 426 .verify = cpufreq_generic_frequency_table_verify,
|
D | exynos5440-cpufreq.c | 311 .verify = cpufreq_generic_frequency_table_verify,
|
D | mt8173-cpufreq.c | 473 .verify = cpufreq_generic_frequency_table_verify,
|
D | s5pv210-cpufreq.c | 574 .verify = cpufreq_generic_frequency_table_verify,
|
D | pmac64-cpufreq.c | 332 .verify = cpufreq_generic_frequency_table_verify,
|
D | powernv-cpufreq.c | 547 .verify = cpufreq_generic_frequency_table_verify,
|
D | powernow-k7.c | 675 .verify = cpufreq_generic_frequency_table_verify,
|
D | arm_big_little.c | 515 .verify = cpufreq_generic_frequency_table_verify,
|
D | pcc-cpufreq.c | 572 .verify = pcc_cpufreq_verify,
|
D | cpufreq.c | 2109 ret = cpufreq_driver->verify(new_policy); in cpufreq_set_policy() 2121 ret = cpufreq_driver->verify(new_policy); in cpufreq_set_policy() 2413 if (!driver_data || !driver_data->verify || !driver_data->init || in cpufreq_register_driver()
|
D | longhaul.c | 915 .verify = cpufreq_generic_frequency_table_verify,
|
D | acpi-cpufreq.c | 900 .verify = cpufreq_generic_frequency_table_verify,
|
D | powernow-k8.c | 1162 .verify = cpufreq_generic_frequency_table_verify,
|
D | intel_pstate.c | 1203 .verify = intel_pstate_verify_policy,
|
/linux-4.4.14/drivers/staging/vt6655/ |
D | TODO | 13 - verify unsigned long usage for x86-64 arch
|
/linux-4.4.14/include/linux/ |
D | ptp_clock_kernel.h | 111 int (*verify)(struct ptp_clock_info *ptp, unsigned int pin, member
|
D | cpufreq.h | 230 int (*verify)(struct cpufreq_policy *policy); member
|
/linux-4.4.14/Documentation/cpu-freq/ |
D | cpu-drivers.txt | 25 1.3 verify 57 cpufreq_driver.verify - A pointer to a "verification" function. 116 cpufreq_driver.verify and either 132 1.3 verify 244 ->verify call.
|
/linux-4.4.14/tools/iio/ |
D | iio_utils.c | 656 int verify) in _write_sysfs_int() argument 690 if (verify) { in _write_sysfs_int() 753 const char *val, int verify) in _write_sysfs_string() argument 788 if (verify) { in _write_sysfs_string()
|
/linux-4.4.14/fs/btrfs/ |
D | Kconfig | 49 writes of the super block). The goal is to verify that the 60 to verify the integrity of (super)-block write requests
|
D | disk-io.c | 279 int verify) in csum_tree_block() argument 315 if (verify) { in csum_tree_block()
|
/linux-4.4.14/Documentation/device-mapper/ |
D | log-writes.txt | 6 to verify the integrity of metadata or data as the file system is written to. 117 <verify md5sum's are correct> 119 Another option is to do a complicated file system operation and verify the file
|
D | verity.txt | 132 It is expected that a user-space tool will verify the integrity of the 160 A command line tool veritysetup is available to compute or verify
|
/linux-4.4.14/scripts/ |
D | setlocalversion | 47 head=`git rev-parse --verify --short HEAD 2>/dev/null`; then
|
/linux-4.4.14/mm/ |
D | Kconfig.debug | 23 fill the pages with poison patterns after free_pages() and verify
|
/linux-4.4.14/Documentation/video4linux/ |
D | extract_xc3028.pl | 27 sub verify ($$) subroutine 1700 verify($sourcefile_24, $hash_24); 1708 verify($sourcefile_27, $hash_27);
|
D | v4l2-framework.txt | 420 bridge driver availability. The subdevice driver then has to verify whether all
|
/linux-4.4.14/include/uapi/scsi/ |
D | cxlflash_ioctl.h | 153 struct dk_cxlflash_verify verify; member
|
/linux-4.4.14/Documentation/networking/ |
D | s2io.txt | 115 b. Ensure Transmit Checksum offload is enabled. Use ethtool to set/verify this 128 set/verify this option.
|
D | multiqueue.txt | 40 blocking. It will cycle though the bands and verify that the hardware queue
|
D | cdc_mbim.txt | 246 /* verify DSS VLAN range */ 251 /* verify ethertype */
|
D | iphase.txt | 63 d. To verify that the 'ia' driver is loaded successfully, run the
|
D | fib_trie.txt | 33 verify that they actually do match the key we are searching for.
|
D | batman-adv.txt | 42 new interfaces to verify the compatibility. There is no need to
|
D | 3c509.txt | 141 have an interrupt line problem. Check /proc/interrupts to verify that the
|
D | decnet.txt | 95 verify with iproute2).
|
D | e1000e.txt | 297 adapters. To verify if a port supports Wake on Lan run ethtool eth<X>.
|
D | rds.txt | 217 RDS's IB transport uses a credit-based mechanism to verify that
|
D | ixgbe.txt | 134 You can verify that the driver is using Flow Director by looking at the counter
|
D | stmmac.txt | 357 restart the ANE, verify Full/Half duplex mode and Speed.
|
D | ixgb.txt | 336 working, verify in the "In This Release" section of the readme that you have
|
D | ip-sysctl.txt | 31 can verify them besides a plain socket lookup. Current 33 and DCCP as they verify e.g. the sequence number or the
|
D | arcnet-hardware.txt | 28 work with 100 Mbps cards, but I haven't been able to verify this myself, 3005 I could, however, only verify two settings...
|
/linux-4.4.14/drivers/gpio/ |
D | gpio-ich.c | 116 static int ichx_write_bit(int reg, unsigned nr, int val, int verify) in ichx_write_bit() argument 143 if (verify && data != tmp) in ichx_write_bit()
|
/linux-4.4.14/crypto/asymmetric_keys/ |
D | Kconfig | 47 signature data and provides the ability to verify the signature.
|
/linux-4.4.14/drivers/input/touchscreen/ |
D | ad7877.c | 685 u16 verify; in ad7877_probe() local 762 verify = ad7877_read(spi, AD7877_REG_SEQ1); in ad7877_probe() 764 if (verify != AD7877_MM_SEQUENCE){ in ad7877_probe()
|
/linux-4.4.14/Documentation/ |
D | SecurityBugs | 10 who will help verify the bug report and develop and release a fix.
|
D | digsig.txt | 12 Digital signature verification API provides a method to verify digital signature.
|
D | intel_txt.txt | 116 verify the kernel and initrd. 167 will re-calculate the MAC and verify it against the sealed value. 205 DRTM process to verify and configure the system. It is signed
|
D | SubmittingDrivers | 60 listed in case it's necessary to verify the will of 93 system-wide suspend and resume transitions. You should verify
|
D | xz.txt | 64 which will verify the integrity of the uncompressed data anyway.
|
D | BUG-HUNTING | 67 . Rebuild a revision that you believe works, install, and verify that.
|
D | printk-formats.txt | 267 Do not use this feature without some mechanism to verify the
|
D | kernel-doc-nano-HOWTO.txt | 358 This makes sense to use when you use !F/!P only and want to verify
|
D | unshare.txt | 275 supported unsharing, verify that the system call correctly
|
D | applying-patches.txt | 95 When patch applies a patch file it attempts to verify the sanity of the
|
D | HOWTO | 520 applied, since they don't take much time or effort to verify for
|
D | kmemcheck.txt | 545 not been initialized. We can verify this using gdb:
|
D | kprobes.txt | 196 optimized region -- Kprobes checks the exception tables to verify this);
|
D | SubmittingPatches | 135 in plain English for the reviewer to verify that the code is behaving
|
/linux-4.4.14/Documentation/timers/ |
D | timer_stats.txt | 10 timer_stats should be used by kernel and userspace developers to verify that
|
D | hrtimers.txt | 151 We used the high-resolution clock subsystem ontop of hrtimers to verify
|
/linux-4.4.14/Documentation/filesystems/ |
D | bfs.txt | 47 Just in case, you can verify that you have done the right thing by checking
|
D | xfs-self-describing-metadata.txt | 18 verify, and this in turn limits the supportable size of an XFS filesystem. 62 hence parse and verify the metadata object. IF we can't independently identify 76 integrity checking. We cannot trust the metadata if we cannot verify that it has 79 block. If we can verify the block contains the metadata it was intended to 320 This will verify the internal structure of the metadata before we go any
|
D | path-lookup.txt | 268 | name: "a.c" | We now take its d_lock, verify d_seq of this 312 verify d_seq, increment refcount).
|
D | vfat.txt | 303 verify that a slot does in fact belong to an 8.3 directory entry by
|
D | porting | 462 taken anymore, so verify that your callbacks do not rely on it (none
|
D | ext2.txt | 280 flags to ext2 also needs to update e2fsck to verify these features.
|
D | coda.txt | 520 open and close and pass the ioctl message _a_n_d to verify that a path in
|
/linux-4.4.14/Documentation/video4linux/cx2341x/ |
D | fw-upload.txt | 48 - Issue status API commands to both firmware images to verify.
|
/linux-4.4.14/arch/parisc/kernel/ |
D | smp.c | 92 #error verify IRQ_OFFSET(IPI_IRQ) is ipi_interrupt() in new IRQ region in ipi_init()
|
/linux-4.4.14/Documentation/ABI/testing/ |
D | sysfs-wusb_cbaf | 22 4. The CM can verify that the device's supported band
|
D | sysfs-block | 43 Indicates whether the block layer should verify the
|
/linux-4.4.14/Documentation/DocBook/ |
D | mtdnand.xml.db | 106 API-verify-bbt-descr
|
D | libata.xml.db | 136 API-ata-scsi-verify-xlat
|
D | device-drivers.xml.db | 511 API-mpt-verify-adapter 1090 API-i2c-verify-client 1096 API-i2c-verify-adapter
|
D | gpu.xml.db | 44 API-drm-vma-node-verify-access
|
/linux-4.4.14/Documentation/ide/ |
D | ChangeLog.ide-floppy.1996-2002 | 30 * Jan 9 01 Userland option to select format verify.
|
/linux-4.4.14/crypto/ |
D | rsa.c | 326 .verify = rsa_verify,
|
/linux-4.4.14/Documentation/scsi/ |
D | qlogicfas.txt | 62 you can do multiple tests on smaller files. Then do a COMP to verify
|
D | BusLogic.txt | 203 Host Adapter not in the following table contact the author beforehand to verify
|
/linux-4.4.14/drivers/ptp/ |
D | ptp_chardev.c | 95 if (info->verify(info, pin, func, chan)) { in ptp_set_pinfunc()
|
/linux-4.4.14/Documentation/zh_CN/ |
D | SubmittingPatches | 172 “simple, localized & easy to verify”,也就是说简单的,局部的和易于检验的。
|
/linux-4.4.14/net/sunrpc/auth_gss/ |
D | gss_rpc_upcall.c | 78 PROC(VERIFY, verify),
|
/linux-4.4.14/Documentation/filesystems/nfs/ |
D | nfs-rdma.txt | 162 In particular, it is a good idea to verify that the RDMA stack 271 To verify that the mount is using RDMA, run "cat /proc/mounts" and check
|
D | nfsroot.txt | 176 log at boot time so that administrators can verify that the correct
|
/linux-4.4.14/drivers/staging/lustre/lustre/obdecho/ |
D | echo_client.c | 1559 int verify; in echo_client_kbrw() local 1563 verify = (ostid_id(&oa->o_oi) != ECHO_PERSISTENT_OBJID && in echo_client_kbrw() 1609 if (verify) in echo_client_kbrw() 1621 verify = 0; in echo_client_kbrw() 1627 if (verify) { in echo_client_kbrw()
|
/linux-4.4.14/drivers/net/ethernet/intel/fm10k/ |
D | fm10k_ptp.c | 434 ptp_caps->verify = fm10k_ptp_verify; in fm10k_ptp_register()
|
/linux-4.4.14/Documentation/RCU/ |
D | lockdep.txt | 91 This would verify cases #2 and #3 above, and furthermore lockdep would
|
D | arrayRCU.txt | 137 * was spinning: here verify that the structure is still valid
|
D | RTFP.txt | 164 and Spin to mechanically verify an optimization to Oleg Nesterov's 1839 ,Title="Using {Promela} and {Spin} to verify parallel algorithms"
|
/linux-4.4.14/drivers/staging/lustre/lustre/ptlrpc/ |
D | sec_null.c | 378 .verify = null_ctx_verify,
|
D | sec_plain.c | 954 .verify = plain_ctx_verify,
|
D | sec.c | 974 LASSERT(ctx->cc_ops->verify); in do_cli_unwrap_reply() 975 rc = ctx->cc_ops->verify(ctx, req); in do_cli_unwrap_reply()
|
/linux-4.4.14/Documentation/driver-model/ |
D | binding.txt | 38 chance to verify that it really does support the hardware, and that
|
D | platform.txt | 51 Note that probe() should in general verify that the specified device hardware
|
D | porting.txt | 119 This allows the compiler to verify type-safety of the operations
|
/linux-4.4.14/Documentation/block/ |
D | data-integrity.txt | 26 is well defined and every node in the I/O path can verify the 242 It is up to the receiver to process them and verify data
|
/linux-4.4.14/Documentation/i2c/ |
D | fault-codes | 76 may verify the device returns *correct* responses, and
|
/linux-4.4.14/arch/x86/ |
D | Kconfig.debug | 349 Enabling this option turns on a quick NMI selftest to verify 363 Some simple tests are run to verify IMR bounds checking, alignment
|
/linux-4.4.14/drivers/staging/lustre/lustre/include/ |
D | lustre_sec.h | 398 int (*verify) (struct ptlrpc_cli_ctx *ctx, member
|
/linux-4.4.14/Documentation/video4linux/bttv/ |
D | Sound-FAQ | 18 You should verify this is correct. If it isn't, you have to pass the
|
/linux-4.4.14/arch/s390/kernel/ |
D | head.S | 314 # verify if all required facilities are supported by the machine
|
/linux-4.4.14/Documentation/blockdev/ |
D | floppy.txt | 178 flushings, and slightly more unreliable. Please verify your
|
D | README.DAC960 | 97 contact the author beforehand to verify that it is or will be supported. 197 verify compatibility. Mylex makes available a hard disk compatibility list at 401 whenever it is desired to verify the consistency of the redundancy
|
/linux-4.4.14/Documentation/x86/ |
D | exception-tables.txt | 6 To protect itself the kernel has to verify this address.
|
D | boot.txt | 103 memory. The boot loader should use the "INT 12h" BIOS call to verify
|
/linux-4.4.14/drivers/crypto/qat/qat_common/ |
D | qat_asym_algs.c | 720 .verify = qat_rsa_enc,
|
/linux-4.4.14/drivers/net/ethernet/intel/igb/ |
D | igb_ptp.c | 1075 adapter->ptp_caps.verify = igb_ptp_verify_pin; in igb_ptp_init()
|
/linux-4.4.14/drivers/net/ethernet/intel/ |
D | Kconfig | 24 To verify that your adapter is supported, find the board ID number
|
/linux-4.4.14/Documentation/power/ |
D | basic-pm-debugging.txt | 182 To verify that the STR works, it is generally more convenient to use the s2ram
|
/linux-4.4.14/Documentation/input/ |
D | input.txt | 253 Doing a "cat /dev/input/mouse0" (c, 13, 32) will verify that a mouse
|
D | joystick.txt | 144 After calibrating the joystick you can verify if you like the new
|
D | sentelic.txt | 597 command to FSP at the end of register writing to verify that the
|
/linux-4.4.14/Documentation/PCI/ |
D | pci.txt | 302 The device driver needs to call pci_request_region() to verify 401 This means the interrupt handler doesn't have to verify
|
/linux-4.4.14/Documentation/powerpc/ |
D | cxlflash.txt | 290 verify and passing along any appropriate information. For now, only
|
/linux-4.4.14/drivers/md/ |
D | Kconfig | 481 This is for use by file system developers wishing to verify that
|
/linux-4.4.14/Documentation/vm/ |
D | hugetlbpage.txt | 109 is still very high. Administrators can verify the number of huge pages
|
/linux-4.4.14/drivers/net/phy/ |
D | dp83640.c | 1042 clock->caps.verify = ptp_dp83640_verify; in dp83640_clock_init()
|
/linux-4.4.14/firmware/keyspan_pda/ |
D | keyspan_pda.S | 651 ;; verify a < 10
|
D | xircom_pgs.S | 689 ;; verify a < 10
|
/linux-4.4.14/drivers/mtd/nand/ |
D | Kconfig | 317 these. The driver will check the MSRs to verify that the
|
/linux-4.4.14/kernel/trace/ |
D | Kconfig | 502 a series of tests are made to verify that the tracer is
|
/linux-4.4.14/arch/arm64/ |
D | Kconfig | 332 The workaround is to verify that the Stage 1 translation
|
/linux-4.4.14/lib/ |
D | Kconfig.debug | 604 The sanity checks verify aspects of the VM such as the memory model 639 Say Y to verify that the per_cpu map being accessed has
|
/linux-4.4.14/drivers/scsi/aic7xxx/ |
D | aic7xxx.reg | 554 * gets set high to verify that the memory port access has been
|
D | aic79xx.seq | 2073 * Wait for the current context to finish to verify that
|
/linux-4.4.14/Documentation/s390/ |
D | Debugging390.txt | 1041 You can do a Q TR to verify this. 1841 to verify that the limit was accepted.
|
/linux-4.4.14/Documentation/cdrom/ |
D | cdrom-standard.tex | 329 function $cdrom_ioctl()$ will verify the appropriate user-memory regions
|
/linux-4.4.14/init/ |
D | Kconfig | 96 $ git rev-parse --verify HEAD
|