Searched full:signed (Results 1 – 25 of 129) sorted by relevance
123456
| /Documentation/admin-guide/ |
| D | module-signing.rst | 11 .. - Signed modules and stripping.
12 .. - Loading signed modules.
24 or modules signed with an invalid key. Module signing increases security by
49 (1) :menuselection:`Require modules to be validly signed`
71 If this is on then modules will be automatically signed during the
73 be signed manually using::
78 (3) :menuselection:`Which hash algorithm should modules be signed with?`
93 than being a module) so that modules signed with that algorithm can have
102 and allow the kernel modules to be signed with a key of your choosing.
212 ``.builtin_trusted_keys`` **if** the new key's X.509 wrapper is validly signed by a key
[all …]
|
| /Documentation/translations/zh_CN/maintainer/ |
| D | modifying-patches.rst | 20 Signed-off-by标签和你的之间添加一行，以指示更改的性质。这没有强制性要求，最
24 Signed-off-by: Random J Developer <random@developer.example.org>
26 Signed-off-by: Lucky K Maintainer <lucky@maintainer.example.org>
|
| /Documentation/trace/ |
| D | uprobetracer.rst | 64 by given type. Prefix 's' and 'u' means those types are signed and unsigned
143 field:unsigned short common_type; offset:0; size:2; signed:0;
144 field:unsigned char common_flags; offset:2; size:1; signed:0;
145 field:unsigned char common_preempt_count; offset:3; size:1; signed:0;
146 field:int common_pid; offset:4; size:4; signed:1;
147 field:int common_padding; offset:8; size:4; signed:1;
149 field:unsigned long __probe_ip; offset:12; size:4; signed:0;
150 field:u32 arg1; offset:16; size:4; signed:0;
151 field:u32 arg2; offset:20; size:4; signed:0;
|
| D | kprobetrace.rst | 88 by given type. Prefix 's' and 'u' means those types are signed and unsigned
223 field:unsigned short common_type; offset:0; size:2; signed:0;
224 field:unsigned char common_flags; offset:2; size:1; signed:0;
225 field:unsigned char common_preempt_count; offset:3; size:1;signed:0;
226 field:int common_pid; offset:4; size:4; signed:1;
228 field:unsigned long __probe_ip; offset:12; size:4; signed:0;
229 field:int __probe_nargs; offset:16; size:4; signed:1;
230 field:unsigned long dfd; offset:20; size:4; signed:0;
231 field:unsigned long filename; offset:24; size:4; signed:0;
232 field:unsigned long flags; offset:28; size:4; signed:0;
[all …]
|
| D | fprobetrace.rst | 102 field:unsigned short common_type; offset:0; size:2; signed:0;
103 field:unsigned char common_flags; offset:2; size:1; signed:0;
104 field:unsigned char common_preempt_count; offset:3; size:1; signed:0;
105 field:int common_pid; offset:4; size:4; signed:1;
107 field:unsigned long __probe_ip; offset:8; size:8; signed:0;
108 field:u64 count; offset:16; size:8; signed:0;
109 field:u64 pos; offset:24; size:8; signed:0;
186 You can see all function arguments and return values are recorded as signed int.
|
| /Documentation/maintainer/ |
| D | pull-requests.rst | 40 that will create a signed tag called ``char-misc-4.15-rc1`` based on the
44 Linus will only accept pull requests based on a signed tag. Other
73 the signed tag, so depending on your workflow, you can either
74 describe your work in the signed tag (which will also automatically
75 make it into the pull request email), or you can make the signed
118 Signed-off-by: Your-name-here <your_email@domain>
124 Now that you have a local signed tag, you need to push it up to where it
164 creating pull requests without a signed tag then ``https://`` may be a
|
| D | modifying-patches.rst | 13 is recommended that you add a line between the last Signed-off-by header and
19 Signed-off-by: Random J Developer <random@developer.example.org>
21 Signed-off-by: Lucky K Maintainer <lucky@maintainer.example.org>
|
| D | configure-git.rst | 7 Documentation/maintainer/pull-requests.rst) should be signed with the
8 developers public GPG key. Signed tags can be created by passing
|
| /Documentation/userspace-api/media/v4l/ |
| D | pixfmt-sdr-cs08.rst | 9 Complex signed 8-bit IQ sample
17 and Q are represented as a 8 bit signed number. I value comes first and
|
| D | pixfmt-sdr-cs14le.rst | 9 Complex signed 14-bit little endian IQ sample
17 and Q are represented as a 14 bit signed little endian number. I value
|
| D | pixfmt-tch-td08.rst | 11 8-bit signed Touch Delta
|
| /Documentation/translations/zh_TW/process/ |
| D | submitting-patches.rst | 325 Signed-off-by: Random J Developer <random@developer.example.org>
328 將會自動完成。撤銷也應當包含“Signed-off-by”， ``git revert -s`` 會幫你搞定。
333 作者簽署之後的任何其他簽署（Signed-off-by:'s）均來自處理和傳遞補丁的人員，但
340 Signed-off-by: 標籤表示簽名者參與了補丁的開發，或者他/她在補丁的傳遞路徑中。
373 Signed-off-by: First Co-Author <first@coauthor.example.org>
375 Signed-off-by: Second Co-Author <second@coauthor.example.org>
376 Signed-off-by: From Author <from@author.example.org>
385 Signed-off-by: Random Co-Author <random@coauthor.example.org>
386 Signed-off-by: From Author <from@author.example.org>
388 Signed-off-by: Submitting Co-Author <sub@coauthor.example.org>
[all …]
|
| D | 5.Posting.rst | 128 - 一個或多個標記行，至少有一個由補丁作者的 Signed-off-by 簽名。標記將在下面
166 - Signed-off-by: 這是一個開發人員的證明，證明他或她有權提交補丁以包含到內核
|
| /Documentation/translations/zh_CN/process/ |
| D | submitting-patches.rst | 324 Signed-off-by: Random J Developer <random@developer.example.org>
327 将会自动完成。撤销也应当包含“Signed-off-by”， ``git revert -s`` 会帮你搞定。
332 作者签署之后的任何其他签署（Signed-off-by:'s）均来自处理和传递补丁的人员，但
339 Signed-off-by: 标签表示签名者参与了补丁的开发，或者他/她在补丁的传递路径中。
372 Signed-off-by: First Co-Author <first@coauthor.example.org>
374 Signed-off-by: Second Co-Author <second@coauthor.example.org>
375 Signed-off-by: From Author <from@author.example.org>
384 Signed-off-by: Random Co-Author <random@coauthor.example.org>
385 Signed-off-by: From Author <from@author.example.org>
387 Signed-off-by: Submitting Co-Author <sub@coauthor.example.org>
[all …]
|
| D | 5.Posting.rst | 125 - 一个或多个标记行，至少有一个由补丁作者的 Signed-off-by 签名。标记将在下面
163 - Signed-off-by: 这是一个开发人员的证明，证明他或她有权提交补丁以包含到内核
|
| /Documentation/translations/ja_JP/ |
| D | SubmittingPatches | 330 Signed-off-by: Random J Developer <random@developer.example.org>
346 Signed-off-by とあなたがその末尾に追加する Signed-off-by の間に、修正を
352 Signed-off-by: Random J Developer <random@developer.example.org>
354 Signed-off-by: Lucky K Maintainer <lucky@maintainer.example.org>
384 「 Signed-off-by: 」タグはその署名者がパッチの開発に関わっていたことやパッチ
394 Acked-by: は Signed-off-by: のように公式なタグではありません。それはメンテナが
483 - 上述した「 Signed-off-by: 」行。これも説明本体と同じくチェン
|
| /Documentation/admin-guide/media/ |
| D | si476x.rst | 137 0x14 freqoff Signed frequency offset in units of
139 0x15 rssi Signed value of RSSI in dBuV
140 0x16 snr Signed RF SNR in dB
141 0x17 issi Signed Image Strength Signal
143 0x18 lassi Signed Low side adjacent Channel
|
| /Documentation/bpf/standardization/ |
| D | instruction-set.rst | 48 s signed
64 numbers and `s16` is a type whose valid values are all the 16-bit signed
205 signed integer offset used with pointer arithmetic, except where
210 signed integer immediate value
255 signed integer offset used with pointer arithmetic, unless
259 signed integer immediate value
265 second signed integer immediate value
381 The division and modulo operations support both unsigned and signed flavors.
388 For signed operations (``SDIV`` and ``SMOD``), for ``ALU``,
389 'imm' is interpreted as a 32-bit signed value. For ``ALU64``, 'imm'
[all …]
|
| /Documentation/input/devices/ |
| D | iforce-protocol.rst | 148 04 Level at end of attack. Signed byte.
160 02 Level. Signed byte.
170 02 Magnitude. Signed byte.
171 03 Offset. Signed byte.
190 The encoding is a bit funny here: For coeffs, these are signed values. The
|
| /Documentation/process/ |
| D | maintainer-pgp-guide.rst | 22 communication channels between developers via PGP-signed email exchange.
663 To address both of these issues, Git introduced PGP integration. Signed
666 tag, while signed commits make it nearly impossible for someone to
681 How to work with signed tags
684 To create a signed tag, simply pass the ``-s`` switch to the tag
693 How to verify signed tags
696 To verify a signed tag, simply use the ``verify-tag`` command::
728 How to work with signed commits
731 It is easy to create signed commits, but it is much more difficult to
737 and will ignore signed commits in any external repositories that they
[all …]
|
| D | submitting-patches.rst | 438 Signed-off-by: Random J Developer <random@developer.example.org>
442 Reverts should also include "Signed-off-by". ``git revert -s`` does that
449 Any further SoBs (Signed-off-by:'s) following the author's SoB are from
459 The Signed-off-by: tag indicates that the signer was involved in the
469 Acked-by: is not as formal as Signed-off-by:. It is a record that the acker
493 followed by a Signed-off-by: of the associated co-author. Standard sign-off
494 procedure applies, i.e. the ordering of Signed-off-by: tags should reflect the
497 Signed-off-by: must always be that of the developer submitting the patch.
507 Signed-off-by: First Co-Author <first@coauthor.example.org>
509 Signed-off-by: Second Co-Author <second@coauthor.example.org>
[all …]
|
| /Documentation/translations/it_IT/process/ |
| D | submitting-patches.rst | 479 Signed-off-by: Random J Developer <random@developer.example.org>
484 includere "Signed-off-by", se usate ``git revert -s`` questo verrà
491 In seguito al SoB (Signed-off-by:) dell'autore ve ne sono altri da
502 L'etichetta Signed-off-by: indica che il firmatario è stato coinvolto nello
513 Acked-by: non è formale come Signed-off-by:. Questo indica che la persona ha
536 dev'essere seguito immediatamente dal Signed-off-by: del corrispondente
538 l'ordine delle etichette Signed-off-by: dovrebbe riflettere il più possibile
541 l'ultimo Signed-off-by: dev'essere quello di colui che ha sottomesso la patch.
552 Signed-off-by: First Co-Author <first@coauthor.example.org>
554 Signed-off-by: Second Co-Author <second@coauthor.example.org>
[all …]
|
| /Documentation/translations/sp_SP/process/ |
| D | submitting-patches.rst | 469 Signed-off-by: Random J Developer <random@developer.example.org>
473 Las reversiones de código también deben incluir "Signed-off-by".
481 Cualquier otro SoB (Signed-off-by:) después del SoB del autor es de
491 La etiqueta Signed-off-by: indica que el firmante estuvo involucrado en el
503 Acked-by: no es tan formal como Signed-off-by:. Es una manera de marcar que
527 Co-developed-by: debe ser inmediatamente seguido de Signed-off-by: del
529 de las etiquetas Signed-off-by: debe reflejar el historial cronológico del
532 Signed-off-by: siempre debe ser del desarrollador que envía el parche.
543 Signed-off-by: Primer coautor <primer@coauthor.example.org>
545 Signed-off-by: Segundo coautor <segundo@coautor.ejemplo.org>
[all …]
|
| /Documentation/driver-api/iio/ |
| D | buffers.rst | 43 * *s* or *u*, specifies if signed (2's complement) or unsigned.
71 two byte little endian signed data, that needs a 4 bits right shift before
|
| /Documentation/hwmon/ |
| D | pc87427.rst | 60 connected. The integer part can be 8-bit or 9-bit, and can be signed or
|
123456