Home
last modified time | relevance | path

Searched refs:verified (Results 1 – 31 of 31) sorted by relevance

/linux-4.1.27/crypto/asymmetric_keys/
Dpkcs7_trust.c45 if (x509->verified) { in pkcs7_validate_trust_one()
47 goto verified; in pkcs7_validate_trust_one()
130 verified: in pkcs7_validate_trust_one()
132 x509->verified = true; in pkcs7_validate_trust_one()
134 p->verified = true; in pkcs7_validate_trust_one()
Dx509_parser.h42 bool verified; member
/linux-4.1.27/Documentation/device-mapper/
Dverity.txt85 dm-verity is meant to be set up as part of a verified boot path. This
91 After instantiation, all hashes will be verified on-demand during
92 disk access. If they cannot be verified up to the root node of the
137 the command-line is verified.
Dcache.txt93 the cache can later be verified, or established through use of the
/linux-4.1.27/drivers/staging/media/lirc/
DTODO.lirc_zilog12 verified that cdev and lirc_dev will take the proper module references on
/linux-4.1.27/Documentation/networking/
Ddriver.txt82 be verified. For example, for ethernet check it with
Dz8530drv.txt214 This is based on information provided by Mike Bilow (and verified
Darcnet-hardware.txt445 - PC110 settings were verified by Stephen A. Wood <saw@cebaf.gov>
/linux-4.1.27/Documentation/devicetree/bindings/arm/
Dfw-cfg.txt37 The presence of the registers can be verified by selecting the "signature" blob
/linux-4.1.27/Documentation/bus-devices/
Dti-gpmc.txt41 Generic timing routine has been verified to work properly on
/linux-4.1.27/Documentation/s390/
Ddriver-model.txt148 verified that the device is not already online.
158 verified that the device is online.
/linux-4.1.27/arch/cris/arch-v32/mm/
Dmmu.S73 ; the TLB contents. The problem and workaround were verified
/linux-4.1.27/Documentation/filesystems/
Dxfs-self-describing-metadata.txt93 metadata block can be verified as being in the correct place without needing to
179 is extensively verified and if it is OK we then update the LSN from the last
342 already extensively verified during writeback in xfs_iflush_int, so the only
Dpath-lookup.txt90 reference is taken on the dentry (while the fields are verified under d_lock),
/linux-4.1.27/Documentation/i2c/
Dfault-codes100 have verified that functionality was supported before it
/linux-4.1.27/Documentation/security/
Dkeys-trusted-encrypted.txt9 in hex ascii for convenience, and are integrity verified.
/linux-4.1.27/net/wireless/
DKconfig87 cannot yet be verified. Regulatory verification may at
/linux-4.1.27/include/linux/
Djbd2.h337 BUFFER_FNS(Verified, verified)
/linux-4.1.27/Documentation/
Dmodule-signing.txt60 signature that can be verified by a public key in the kernel's possession
Dintel_txt.txt40 uses Intel TXT to perform a measured and verified launch of an OS
DSubmittingPatches216 change that can be verified by reviewers. Each patch should be justifiable
/linux-4.1.27/Documentation/x86/
Dexception-tables.txt12 This function verified that the memory area starting at address
/linux-4.1.27/Documentation/ia64/
Dmca.txt180 If the previous task has been verified and converted to a blocked
/linux-4.1.27/Documentation/block/
Ddata-integrity.txt175 to be verified upon completion.
/linux-4.1.27/Documentation/fmc/
Dcarrier.txt217 by a driver that has verified the `carrier_name' field.
/linux-4.1.27/Documentation/development-process/
D5.Posting91 verified to do what it says it does.
/linux-4.1.27/Documentation/scheduler/
Dsched-deadline.txt80 this condition is verified, the scheduling deadline and the
/linux-4.1.27/Documentation/cdrom/
Dcdrom-standard.tex727 it is verified that a disc is in the drive and, if $CDO_CHECK_TYPE$ is
/linux-4.1.27/lib/
DKconfig.debug1563 verified for functionality.
/linux-4.1.27/init/
DKconfig1756 userspace may only add extra keys if those keys can be verified by
/linux-4.1.27/arch/x86/
DKconfig770 here unless you have verified that your setup is not