Searched full:private (Results 1 – 25 of 167) sorted by relevance
1234567
| /Documentation/admin-guide/ |
| D | module-signing.rst | 14 .. - Administering/protecting the private key.
102 The string provided should identify a file containing both a private key
106 certificate and a private key.
108 If the PEM file containing the private key is encrypted, or if the
129 private key is used to generate a signature and the corresponding public key is
130 used to check it. The private key is only needed during the build, after which
164 It is also possible to manually generate the key private/public files using the
167 generate the public/private key files::
219 2. The private key filename or PKCS#11 URI
232 If the private key requires a passphrase or PIN, it can be provided in the
[all …]
|
| D | security-bugs.rst | 15 <security@kernel.org>. This is a private list of security officers
63 escalations, may need to be coordinated with the private
80 assigned ahead of public disclosure, they will need to contact the private
|
| /Documentation/networking/ |
| D | 6lowpan.txt | 2 Netdev private dataroom for 6lowpan interfaces:
11 Where LL_PRIV_6LOWPAN_DATA is sizeof linklayer 6lowpan private data struct.
25 Example to evaluate the private usually you can do:
|
| D | ipvlan.txt | 28 FLAGS: bridge (default) | private | vepa
36 (c) This command will create an IPvlan device in L2 private mode.
37 bash# ip link add link eth0 name ipvlan type ipvlan mode l2 private
78 5.2 private:
79 If this option is added to the command-line, the port is set in private
|
| D | z8530book.rst | 73 Set chanA.dev to point to the device structure itself. The private and
74 name field you may use as you wish. The private field is unused by the
114 device points to your private data - you will need to be able to find
115 your private data from this.
119 private field of the network device. The network device fields of the
|
| /Documentation/filesystems/ |
| D | sharedsubtree.txt | 35 c. private mount
119 2c) A private mount does not forward or receive propagation.
124 2d) A unbindable mount is a unbindable private mount
145 mount --make-private mountpoint
241 4) private
297 (4) Private mount
299 A 'private mount' is defined as vfsmount that does not
313 | |make-shared | make-slave | make-private |make-unbindab|
315 |shared |shared |*slave/private| private | unbindable |
318 |slave |shared | **slave | private | unbindable |
[all …]
|
| D | seq_file.txt | 77 iterator can be stored in the private data area and continue from one
119 For more complicated applications, the private field of the seq_file
260 private field of the seq_file structure; that value can then be retrieved
265 private field of the seq_file structure, returning 0 on success. The
309 seq_file private field to kfree() before releasing the structure.
356 value given to single_open() can be found in the private field of the
|
| /Documentation/media/v4l-drivers/ |
| D | omap3isp.rst | 103 Private IOCTLs
111 In general, there is a private ioctl for configuring each of the blocks
114 The following private IOCTLs are supported:
129 While it is possible to use the ISP driver without any use of these private
132 appropriate private IOCTLs.
202 the user from the statistics subdev nodes using private IOCTLs.
204 The private IOCTLs offered by the AEWB, AF and histogram subdevs are heavily
212 This private IOCTL enables/disables a statistic module. If this request is
223 configure private IOCTLs require explanation for better understanding as they
|
| D | meye.rst | 23 MJPEG hardware grabbing is supported via a private API (see below).
90 Private API
96 Besides the video4linux interface, the driver has a private interface
134 - 'motioneye' still uses the meye private v4l1 API extensions.
|
| /Documentation/vm/ |
| D | hugetlbfs_reserv.rst | 82 Reservation Map Location (Private or Shared)
85 A huge page mapping or segment is either private or shared. If private,
91 - For private mappings, the reservation map hangs off the VMA structure.
123 One of the big differences between PRIVATE and SHARED mappings is the way
129 - For private mappings, the lack of an entry in the reservation map indicates
135 For private mappings, hugetlb_reserve_pages() creates the reservation map and
140 are needed for the current mapping/segment. For private mappings, this is
169 file_region will exist that includes the range 'from' - 'to'. For private
236 After obtaining a new huge page, (page)->private is set to the value of
245 was no reservation in a shared mapping or this was a private mapping a new
[all …]
|
| D | overcommit-accounting.rst | 60 | PRIVATE WRITABLE - size of mapping per instance
64 | PRIVATE READ-only - 0 cost (but of little use)
65 | PRIVATE WRITABLE - size of mapping per instance
|
| /Documentation/doc-guide/ |
| D | parse-headers.rst | 155 ignore symbol PRIVATE
160 enum foo { BAR1, BAR2, PRIVATE };
162 It won't generate cross-references for \ **PRIVATE**\ .
170 enum foo { BAR1, BAR2, PRIVATE };
|
| /Documentation/fpga/ |
| D | dfl.rst | 24 FPGA Interface Unit (FIU), Accelerated Function Unit (AFU) and Private Features,
30 | FIU | | | Private | | | Private | | | Private |
62 Private Features represent sub features of the FIU and AFU. They could be
63 various function blocks with different IDs, but all private features which
67 Each FIU, AFU and Private Feature could implement its own functional registers.
69 e.g. FME Header Register Set, and the one for Private Feature, is named as
180 (FPGA base region), discover feature devices and their private features from the
183 also abstracts operations for the private features and exposes common ops to
381 Add new private features support
383 In some cases, we may need to add some new private features to existing FIUs
[all …]
|
| /Documentation/translations/it_IT/doc-guide/ |
| D | parse-headers.rst | 161 ignore symbol PRIVATE
166 enum foo { BAR1, BAR2, PRIVATE };
168 Non genererà alcun riferimento per \ **PRIVATE**\ .
176 enum foo { BAR1, BAR2, PRIVATE };
|
| /Documentation/devicetree/bindings/soc/fsl/ |
| D | qman.txt | 8 - QMan Private Memory Nodes
66 Definition: List of phandles referencing the QMan private memory
79 QMan Private Memory Nodes
109 The following constraints are relevant to the FQD and PFDR private memory:
|
| D | bman.txt | 8 - BMan Private Memory Node
65 BMan Private Memory Node
82 The following constraints are relevant to the FBPR private memory:
|
| /Documentation/x86/ |
| D | amd-memory-encryption.rst | 18 within the VM itself. SEV guest VMs have the concept of private and shared
19 memory. Private memory is encrypted with the guest-specific key, while shared
37 as private. All the DMA operations inside the guest must be performed on shared
|
| /Documentation/process/ |
| D | maintainer-pgp-guide.rst | 99 of caching the private key passphrase. There are two options you should
169 lose your private subkey, it cannot be recreated from the master key
205 GnuPG uses passphrases to encrypt your private keys before storing them on
207 its entirety, the attackers cannot use your private keys without first
210 It is absolutely essential that your private keys are protected by a
254 The best way to create a printable hardcopy of your private key is by
260 Run the following command to create a hardcopy backup of your private
365 $ cd ~/.gnupg/private-keys-v1.d
374 $ cd ~/.gnupg/private-keys-v1.d
390 If you don't have the "private-keys-v1.d" directory
[all …]
|
| D | code-of-conduct.rst | 34 * Public or private harassment
35 * Publishing others’ private information, such as a physical or electronic
|
| /Documentation/devicetree/bindings/net/can/ |
| D | m_can.txt | 23 private Message RAM are used by this M_CAN controller.
30 usually set to 0x0 if you're using a private Message
|
| /Documentation/devicetree/bindings/sound/ |
| D | omap-dmic.txt | 15 reg = <0x4012e000 0x7f>, /* MPU private access */
|
| D | omap-mcpdm.txt | 17 reg = <0x40132000 0x7f>, /* MPU private access */
|
| /Documentation/ioctl/ |
| D | botching-up-ioctls.rst | 184 default pick a private per-fd namespace which forces any sharing to be done
189 namespace, private by default, for framebuffers would have been more
207 * Think hard whether you really want a driver-private interface. Of course
208 it's much quicker to push a driver-private interface than engaging in
210 private interface to spearhead a new concept is what's required. But in the
|
| /Documentation/s390/ |
| D | driver-model.rst | 88 struct ccw_device_private *private;
111 The 'private' field contains data needed for internal i/o operation only, and
133 is interested in. The driver should only allocate private structures
176 down the device, but not de-allocate its private data.
261 private data.
|
| /Documentation/gpu/ |
| D | drm-kms.rst | 147 point, but are generally linked to the driver private structure that embeds
212 "drm_atomic_state" -> "duplicated driver private state"
223 "drm_device" -> "driver private object"
229 "driver private object" -> "driver private state"
267 container. Driver private state structures are also tracked in the same
275 Handling Driver Private State
279 :doc: handling driver private state
|
1234567