Home
last modified time | relevance | path

Searched refs:verify (Results 1 – 191 of 191) sorted by relevance

/linux-4.1.27/Documentation/dvb/
Dget_dvb_firmware73 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.1.27/tools/testing/selftests/sysctl/
Dcommon_tests17 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
Drun_stringtests16 if ! verify "${TARGET}"; then
26 if verify "${TARGET}"; then
/linux-4.1.27/arch/sparc/boot/
Dinstall.sh20 verify () { function
31 verify "$2"
32 verify "$3"
/linux-4.1.27/arch/nios2/boot/
Dinstall.sh20 verify () { function
31 verify "$2"
32 verify "$3"
/linux-4.1.27/arch/m68k/
Dinstall.sh20 verify () { function
31 verify "$2"
32 verify "$3"
/linux-4.1.27/arch/parisc/
Dinstall.sh22 verify () { function
34 verify "$2"
35 verify "$3"
/linux-4.1.27/arch/blackfin/boot/
Dinstall.sh23 verify () { function
34 verify "$2"
35 verify "$3"
/linux-4.1.27/arch/arm/boot/
Dinstall.sh23 verify () { function
34 verify "$2"
35 verify "$3"
/linux-4.1.27/drivers/net/ethernet/mellanox/mlx4/
Dcmd.c1052 .verify = NULL,
1061 .verify = NULL,
1070 .verify = NULL,
1079 .verify = NULL,
1088 .verify = NULL,
1097 .verify = NULL,
1106 .verify = NULL,
1115 .verify = NULL,
1124 .verify = NULL,
1133 .verify = NULL,
[all …]
Dmlx4.h200 int (*verify)(struct mlx4_dev *dev, int slave, struct mlx4_vhcr *vhcr, member
/linux-4.1.27/arch/x86/boot/
Dinstall.sh20 verify () { function
31 verify "$2"
32 verify "$3"
/linux-4.1.27/drivers/mtd/tests/
Dmtd_nandecctest.c29 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.1.27/drivers/net/ethernet/microchip/
DKconfig32 bool "Enable write verify"
35 Enable the verify after the buffer write useful for debugging purpose.
/linux-4.1.27/drivers/md/bcache/
Dsysfs.c99 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()
Dbcache.h368 unsigned verify:1; member
674 unsigned verify:1; member
Drequest.c33 static bool verify(struct cached_dev *dc, struct bio *bio) in verify() function
35 return dc->verify; in verify()
745 if (verify(dc, &s->bio.bio) && s->recoverable && !s->read_dirty_data) in cached_dev_read_done()
770 else if (s->iop.bio || verify(dc, &s->bio.bio)) in cached_dev_read_done_bh()
Ddebug.c36 if (!b->c->verify || !b->c->verify_ondisk) in bch_btree_verify()
/linux-4.1.27/Documentation/fmc/
Dfmc-trivial.txt5 interrupt handler. I used it to verify the basic mechanism of the FMC
Dfmc-fakedev.txt15 You can also use this device to verify the match algorithms, by asking
/linux-4.1.27/fs/nfsd/
Dnfs4proc.c1112 struct nfsd4_verify *verify) in _nfsd4_verify() argument
1122 status = check_attr_support(rqstp, cstate, verify->ve_bmval, NULL); in _nfsd4_verify()
1126 if ((verify->ve_bmval[0] & FATTR4_WORD0_RDATTR_ERROR) in _nfsd4_verify()
1127 || (verify->ve_bmval[1] & NFSD_WRITEONLY_ATTRS_WORD1)) in _nfsd4_verify()
1129 if (verify->ve_attrlen & 3) in _nfsd4_verify()
1135 count = 4 + (verify->ve_attrlen >> 2); in _nfsd4_verify()
1144 verify->ve_bmval, in _nfsd4_verify()
1158 if (ntohl(*p++) != verify->ve_attrlen) in _nfsd4_verify()
1160 if (!memcmp(p, verify->ve_attrval, verify->ve_attrlen)) in _nfsd4_verify()
1170 struct nfsd4_verify *verify) in nfsd4_nverify() argument
[all …]
Dxdr4.h535 struct nfsd4_verify verify; member
Dnfs4xdr.c1188 nfsd4_decode_verify(struct nfsd4_compoundargs *argp, struct nfsd4_verify *verify) in nfsd4_decode_verify() argument
1192 if ((status = nfsd4_decode_bitmap(argp, verify->ve_bmval))) in nfsd4_decode_verify()
1199 verify->ve_attrlen = be32_to_cpup(p++); in nfsd4_decode_verify()
1200 READ_BUF(verify->ve_attrlen); in nfsd4_decode_verify()
1201 SAVEMEM(verify->ve_attrval, verify->ve_attrlen); in nfsd4_decode_verify()
/linux-4.1.27/drivers/cpufreq/
Ddbx500-cpufreq.c38 .verify = cpufreq_generic_frequency_table_verify,
Dunicore2-cpufreq.c68 .verify = ucv2_verify_speed,
Dcris-etraxfs-cpufreq.c57 .verify = cpufreq_generic_frequency_table_verify,
Dsc520_freq.c93 .verify = cpufreq_generic_frequency_table_verify,
Dcris-artpec3-cpufreq.c57 .verify = cpufreq_generic_frequency_table_verify,
Dsa1100-cpufreq.c205 .verify = cpufreq_generic_frequency_table_verify,
Delanfreq.c197 .verify = cpufreq_generic_frequency_table_verify,
Dppc_cbe_cpufreq.c142 .verify = cpufreq_generic_frequency_table_verify,
Dat32ap-cpufreq.c117 .verify = cpufreq_generic_frequency_table_verify,
Dsfi-cpufreq.c83 .verify = cpufreq_generic_frequency_table_verify,
Dloongson2_cpufreq.c114 .verify = cpufreq_generic_frequency_table_verify,
Dmaple-cpufreq.c151 .verify = cpufreq_generic_frequency_table_verify,
Dtegra-cpufreq.c169 .verify = cpufreq_generic_frequency_table_verify,
Dblackfin-cpufreq.c194 .verify = cpufreq_generic_frequency_table_verify,
Ds3c64xx-cpufreq.c216 .verify = cpufreq_generic_frequency_table_verify,
Domap-cpufreq.c153 .verify = cpufreq_generic_frequency_table_verify,
Dsh-cpufreq.c155 .verify = sh_cpufreq_verify,
Ddavinci-cpufreq.c124 .verify = davinci_verify_speed,
Dkirkwood-cpufreq.c98 .verify = cpufreq_generic_frequency_table_verify,
Dspear-cpufreq.c163 .verify = cpufreq_generic_frequency_table_verify,
Dsparc-us3-cpufreq.c195 driver->verify = cpufreq_generic_frequency_table_verify; in us3_freq_init()
Dp4-clockmod.c237 .verify = cpufreq_generic_frequency_table_verify,
Dintegrator-cpufreq.c194 .verify = integrator_verify_policy,
Dpasemi-cpufreq.c264 .verify = cpufreq_generic_frequency_table_verify,
Dpowernow-k6.c249 .verify = cpufreq_generic_frequency_table_verify,
Dspeedstep-ich.c311 .verify = cpufreq_generic_frequency_table_verify,
Dexynos-cpufreq.c146 .verify = cpufreq_generic_frequency_table_verify,
Dpxa3xx-cpufreq.c205 .verify = cpufreq_generic_frequency_table_verify,
Dlongrun.c282 .verify = longrun_verify_policy,
Dspeedstep-smi.c292 .verify = cpufreq_generic_frequency_table_verify,
Dls1x-cpufreq.c122 .verify = cpufreq_generic_frequency_table_verify,
Dsa1110-cpufreq.c316 .verify = cpufreq_generic_frequency_table_verify,
Dcpufreq-nforce2.c374 .verify = nforce2_verify,
Dsparc-us2e-cpufreq.c336 driver->verify = cpufreq_generic_frequency_table_verify; in us2e_freq_init()
Dpowernv-cpufreq.c410 .verify = cpufreq_generic_frequency_table_verify,
Dpxa2xx-cpufreq.c427 .verify = cpufreq_generic_frequency_table_verify,
Dia64-acpi-cpufreq.c345 .verify = cpufreq_generic_frequency_table_verify,
Dqoriq-cpufreq.c319 .verify = cpufreq_generic_frequency_table_verify,
Dgx-suspmod.c442 .verify = cpufreq_gx_verify,
Dimx6q-cpufreq.c147 .verify = cpufreq_generic_frequency_table_verify,
Dcpufreq-dt.c364 .verify = cpufreq_generic_frequency_table_verify,
De_powersaver.c391 .verify = cpufreq_generic_frequency_table_verify,
Ds3c2416-cpufreq.c479 .verify = cpufreq_generic_frequency_table_verify,
Dpmac32-cpufreq.c437 .verify = cpufreq_generic_frequency_table_verify,
Dspeedstep-centrino.c510 .verify = cpufreq_generic_frequency_table_verify,
Dexynos5440-cpufreq.c311 .verify = cpufreq_generic_frequency_table_verify,
Dpmac64-cpufreq.c332 .verify = cpufreq_generic_frequency_table_verify,
Ds5pv210-cpufreq.c574 .verify = cpufreq_generic_frequency_table_verify,
Dpowernow-k7.c675 .verify = cpufreq_generic_frequency_table_verify,
Darm_big_little.c501 .verify = cpufreq_generic_frequency_table_verify,
Dpcc-cpufreq.c572 .verify = pcc_cpufreq_verify,
Dcpufreq.c2165 ret = cpufreq_driver->verify(new_policy); in cpufreq_set_policy()
2181 ret = cpufreq_driver->verify(new_policy); in cpufreq_set_policy()
2419 if (!driver_data || !driver_data->verify || !driver_data->init || in cpufreq_register_driver()
Dlonghaul.c915 .verify = cpufreq_generic_frequency_table_verify,
Dacpi-cpufreq.c887 .verify = cpufreq_generic_frequency_table_verify,
Dpowernow-k8.c1170 .verify = cpufreq_generic_frequency_table_verify,
Dintel_pstate.c1053 .verify = intel_pstate_verify_policy,
/linux-4.1.27/tools/iio/
Diio_utils.c489 int _write_sysfs_int(char *filename, char *basedir, int val, int verify) in _write_sysfs_int() argument
507 if (verify) { in _write_sysfs_int()
539 int _write_sysfs_string(char *filename, char *basedir, char *val, int verify) in _write_sysfs_string() argument
558 if (verify) { in _write_sysfs_string()
/linux-4.1.27/drivers/staging/vt6655/
DTODO13 - verify unsigned long usage for x86-64 arch
/linux-4.1.27/include/linux/
Dptp_clock_kernel.h111 int (*verify)(struct ptp_clock_info *ptp, unsigned int pin, member
Dcpufreq.h227 int (*verify)(struct cpufreq_policy *policy); member
/linux-4.1.27/Documentation/cpu-freq/
Dcpu-drivers.txt25 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.1.27/fs/btrfs/
DKconfig49 writes of the super block). The goal is to verify that the
60 to verify the integrity of (super)-block write requests
Ddisk-io.c279 int verify) in csum_tree_block() argument
315 if (verify) { in csum_tree_block()
/linux-4.1.27/Documentation/device-mapper/
Dlog-writes.txt6 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
Dverity.txt132 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.1.27/scripts/
Dsetlocalversion47 head=`git rev-parse --verify --short HEAD 2>/dev/null`; then
/linux-4.1.27/fs/ext4/
Dballoc.c431 goto verify; in ext4_read_block_bitmap_nowait()
436 goto verify; in ext4_read_block_bitmap_nowait()
459 goto verify; in ext4_read_block_bitmap_nowait()
470 verify: in ext4_read_block_bitmap_nowait()
Dialloc.c143 goto verify; in ext4_read_inode_bitmap()
148 goto verify; in ext4_read_inode_bitmap()
170 goto verify; in ext4_read_inode_bitmap()
188 verify: in ext4_read_inode_bitmap()
/linux-4.1.27/mm/
DKconfig.debug23 fill the pages with poison patterns after free_pages() and verify
/linux-4.1.27/Documentation/video4linux/
Dextract_xc3028.pl27 sub verify ($$) subroutine
1700 verify($sourcefile_24, $hash_24);
1708 verify($sourcefile_27, $hash_27);
Dv4l2-framework.txt420 bridge driver availability. The subdevice driver then has to verify whether all
/linux-4.1.27/Documentation/networking/
Ds2io.txt115 b. Ensure Transmit Checksum offload is enabled. Use ethtool to set/verify this
128 set/verify this option.
Dmultiqueue.txt40 blocking. It will cycle though the bands and verify that the hardware queue
Dcdc_mbim.txt246 /* verify DSS VLAN range */
251 /* verify ethertype */
Diphase.txt63 d. To verify that the 'ia' driver is loaded successfully, run the
Dfib_trie.txt33 verify that they actually do match the key we are searching for.
Dbatman-adv.txt42 new interfaces to verify the compatibility. There is no need to
D3c509.txt141 have an interrupt line problem. Check /proc/interrupts to verify that the
Ddecnet.txt95 verify with iproute2).
De1000e.txt297 adapters. To verify if a port supports Wake on Lan run ethtool eth<X>.
Dixgbe.txt134 You can verify that the driver is using Flow Director by looking at the counter
Drds.txt217 RDS's IB transport uses a credit-based mechanism to verify that
Dstmmac.txt367 restart the ANE, verify Full/Half duplex mode and Speed.
Dixgb.txt336 working, verify in the "In This Release" section of the readme that you have
Dip-sysctl.txt31 can verify them besides a plain socket lookup. Current
33 and DCCP as they verify e.g. the sequence number or the
Darcnet-hardware.txt28 work with 100 Mbps cards, but I haven't been able to verify this myself,
3005 I could, however, only verify two settings...
Dbonding.txt1797 The ARP monitor relies on the device driver itself to verify
/linux-4.1.27/drivers/gpio/
Dgpio-ich.c116 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.1.27/crypto/asymmetric_keys/
DKconfig47 signature data and provides the ability to verify the signature.
/linux-4.1.27/drivers/input/touchscreen/
Dad7877.c685 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.1.27/Documentation/
DSecurityBugs10 who will help verify the bug report and develop and release a fix.
Ddigsig.txt12 Digital signature verification API provides a method to verify digital signature.
Dintel_txt.txt116 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
DSubmittingDrivers60 listed in case it's necessary to verify the will of
93 system-wide suspend and resume transitions. You should verify
Dxz.txt64 which will verify the integrity of the uncompressed data anyway.
DBUG-HUNTING67 . Rebuild a revision that you believe works, install, and verify that.
Dprintk-formats.txt259 Do not use this feature without some mechanism to verify the
Dkernel-doc-nano-HOWTO.txt358 This makes sense to use when you use !F/!P only and want to verify
Dunshare.txt275 supported unsharing, verify that the system call correctly
Dapplying-patches.txt95 When patch applies a patch file it attempts to verify the sanity of the
DHOWTO520 applied, since they don't take much time or effort to verify for
Dkmemcheck.txt545 not been initialized. We can verify this using gdb:
Dkprobes.txt196 optimized region -- Kprobes checks the exception tables to verify this);
DSubmittingPatches135 in plain English for the reviewer to verify that the code is behaving
/linux-4.1.27/Documentation/filesystems/
Dbfs.txt47 Just in case, you can verify that you have done the right thing by checking
Dxfs-self-describing-metadata.txt18 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
Dpath-lookup.txt268 | name: "a.c" | We now take its d_lock, verify d_seq of this
312 verify d_seq, increment refcount).
Dvfat.txt303 verify that a slot does in fact belong to an 8.3 directory entry by
Dporting462 taken anymore, so verify that your callbacks do not rely on it (none
Dext2.txt280 flags to ext2 also needs to update e2fsck to verify these features.
Dcoda.txt520 open and close and pass the ioctl message _a_n_d to verify that a path in
/linux-4.1.27/arch/parisc/kernel/
Dsmp.c92 #error verify IRQ_OFFSET(IPI_IRQ) is ipi_interrupt() in new IRQ region in ipi_init()
/linux-4.1.27/Documentation/video4linux/cx2341x/
Dfw-upload.txt48 - Issue status API commands to both firmware images to verify.
/linux-4.1.27/Documentation/timers/
Dtimer_stats.txt10 timer_stats should be used by kernel and userspace developers to verify that
Dhrtimers.txt151 We used the high-resolution clock subsystem ontop of hrtimers to verify
/linux-4.1.27/Documentation/ABI/testing/
Dsysfs-wusb_cbaf22 4. The CM can verify that the device's supported band
Dsysfs-block43 Indicates whether the block layer should verify the
/linux-4.1.27/Documentation/ide/
DChangeLog.ide-floppy.1996-200230 * Jan 9 01 Userland option to select format verify.
/linux-4.1.27/net/sunrpc/auth_gss/
Dgss_rpc_upcall.c78 PROC(VERIFY, verify),
/linux-4.1.27/drivers/ptp/
Dptp_chardev.c95 if (info->verify(info, pin, func, chan)) { in ptp_set_pinfunc()
/linux-4.1.27/Documentation/scsi/
Dqlogicfas.txt62 you can do multiple tests on smaller files. Then do a COMP to verify
DBusLogic.txt203 Host Adapter not in the following table contact the author beforehand to verify
/linux-4.1.27/Documentation/zh_CN/
DSubmittingPatches172 “simple, localized & easy to verify”，也就是说简单的，局部的和易于检验的。
/linux-4.1.27/Documentation/filesystems/nfs/
Dnfs-rdma.txt162 In particular, it is a good idea to verify that the RDMA stack
273 To verify that the mount is using RDMA, run "cat /proc/mounts" and check
Dnfsroot.txt173 log at boot time so that administrators can verify that the correct
/linux-4.1.27/drivers/staging/lustre/lustre/obdecho/
Decho_client.c1558 int verify; in echo_client_kbrw() local
1562 verify = (ostid_id(&oa->o_oi) != ECHO_PERSISTENT_OBJID && in echo_client_kbrw()
1608 if (verify) in echo_client_kbrw()
1620 verify = 0; in echo_client_kbrw()
1626 if (verify) { in echo_client_kbrw()
/linux-4.1.27/Documentation/driver-model/
Dbinding.txt38 chance to verify that it really does support the hardware, and that
Dplatform.txt51 Note that probe() should in general verify that the specified device hardware
Dporting.txt119 This allows the compiler to verify type-safety of the operations
/linux-4.1.27/drivers/net/ethernet/intel/fm10k/
Dfm10k_ptp.c433 ptp_caps->verify = fm10k_ptp_verify; in fm10k_ptp_register()
/linux-4.1.27/drivers/staging/lustre/lustre/ptlrpc/
Dsec_null.c376 .verify = null_ctx_verify,
Dsec_plain.c955 .verify = plain_ctx_verify,
Dsec.c1016 LASSERT(ctx->cc_ops->verify); in do_cli_unwrap_reply()
1017 rc = ctx->cc_ops->verify(ctx, req); in do_cli_unwrap_reply()
/linux-4.1.27/arch/x86/
DKconfig.debug304 Enabling this option turns on a quick NMI selftest to verify
318 Some simple tests are run to verify IMR bounds checking, alignment
/linux-4.1.27/Documentation/RCU/
Dlockdep.txt101 This would verify cases #2 and #3 above, and furthermore lockdep would
DarrayRCU.txt125 * was spinning: here verify that the structure is still valid
DRTFP.txt164 and Spin to mechanically verify an optimization to Oleg Nesterov's
1839 ,Title="Using {Promela} and {Spin} to verify parallel algorithms"
/linux-4.1.27/Documentation/block/
Ddata-integrity.txt26 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.1.27/Documentation/i2c/
Dfault-codes76 may verify the device returns *correct* responses, and
/linux-4.1.27/Documentation/video4linux/bttv/
DSound-FAQ18 You should verify this is correct. If it isn't, you have to pass the
/linux-4.1.27/drivers/staging/lustre/lustre/include/
Dlustre_sec.h415 int (*verify) (struct ptlrpc_cli_ctx *ctx, member
/linux-4.1.27/security/
Dsecurity.c41 static inline int __init verify(struct security_operations *ops) in verify() function
122 if (verify(ops)) { in register_security()
/linux-4.1.27/Documentation/blockdev/
Dfloppy.txt178 flushings, and slightly more unreliable. Please verify your
DREADME.DAC96097 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.1.27/Documentation/x86/
Dexception-tables.txt6 To protect itself the kernel has to verify this address.
Dboot.txt103 memory. The boot loader should use the "INT 12h" BIOS call to verify
/linux-4.1.27/Documentation/power/
Dbasic-pm-debugging.txt182 To verify that the STR works, it is generally more convenient to use the s2ram
/linux-4.1.27/Documentation/input/
Dinput.txt253 Doing a "cat /dev/input/mouse0" (c, 13, 32) will verify that a mouse
Djoystick.txt144 After calibrating the joystick you can verify if you like the new
Dsentelic.txt597 command to FSP at the end of register writing to verify that the
/linux-4.1.27/drivers/net/ethernet/intel/
DKconfig26 To verify that your adapter is supported, find the board ID number
/linux-4.1.27/drivers/staging/i2o/
DREADME.ioctl298 *(sw->swlen) value to verify correct identication of the module to remove.
/linux-4.1.27/drivers/net/ethernet/intel/igb/
Digb_ptp.c1043 adapter->ptp_caps.verify = igb_ptp_verify_pin; in igb_ptp_init()
/linux-4.1.27/Documentation/PCI/
Dpci.txt302 The device driver needs to call pci_request_region() to verify
401 This means the interrupt handler doesn't have to verify
/linux-4.1.27/drivers/mtd/nand/
DKconfig320 these. The driver will check the MSRs to verify that the
/linux-4.1.27/drivers/md/
DKconfig468 This is for use by file system developers wishing to verify that
/linux-4.1.27/drivers/net/phy/
Ddp83640.c1030 clock->caps.verify = ptp_dp83640_verify; in dp83640_clock_init()
/linux-4.1.27/firmware/keyspan_pda/
Dkeyspan_pda.S651 ;; verify a < 10
Dxircom_pgs.S689 ;; verify a < 10
/linux-4.1.27/Documentation/vm/
Dhugetlbpage.txt109 is still very high. Administrators can verify the number of huge pages
/linux-4.1.27/kernel/trace/
DKconfig502 a series of tests are made to verify that the tracer is
/linux-4.1.27/lib/
DKconfig.debug594 The sanity checks verify aspects of the VM such as the memory model
629 Say Y to verify that the per_cpu map being accessed has
/linux-4.1.27/drivers/scsi/aic7xxx/
Daic7xxx.reg554 * gets set high to verify that the memory port access has been
Daic79xx.seq2073 * Wait for the current context to finish to verify that
/linux-4.1.27/Documentation/s390/
DDebugging390.txt1041 You can do a Q TR to verify this.
1841 to verify that the limit was accepted.
/linux-4.1.27/Documentation/cdrom/
Dcdrom-standard.tex329 function $cdrom_ioctl()$ will verify the appropriate user-memory regions
/linux-4.1.27/init/
DKconfig96 $ git rev-parse --verify HEAD
/linux-4.1.27/Documentation/sound/oss/
DREADME.OSS176 release of the driver (see Readme). Also verify