Home
last modified time | relevance | path

Searched refs:Signed (Results 1 – 25 of 55) sorted by relevance

123

/linux/rust/kernel/
H A Dnum.rs14 pub enum Signed {} enum
73 i8: Signed,
74 i16: Signed,
75 i32: Signed,
76 i64: Signed,
77 i128: Signed,
78 isize: Signed
/linux/Documentation/translations/zh_TW/process/
H A Dsubmitting-patches.rst325 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: 標籤表示簽名者參與了補丁的開發，或者他/她在補丁的傳遞路徑中。
362 簽署程序要求Signed-off-by:標籤的順序應儘可能反映補丁的時間歷史，無論作者是通
363 過From:還是Co-developed-by:表明。值得注意的是，最後一個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>
[all …]
H A D5.Posting.rst128 - 一個或多個標記行，至少有一個由補丁作者的 Signed-off-by 簽名。標記將在下面
162 - Signed-off-by: 這是一個開發人員的證明，證明他或她有權提交補丁以包含到內核
170 的Signed-off-by之後。具體內容和示例見以下文件
H A D3.Early-stage.rst116 誰會在這些補丁上加上Signed-off-by行簽名（如有）。這些人將是幫助新開發項目的
/linux/Documentation/translations/zh_CN/process/
H A Dsubmitting-patches.rst321 Signed-off-by: Random J Developer <random@developer.example.org>
324 将会自动完成。撤销也应当包含“Signed-off-by”， ``git revert -s`` 会帮你搞定。
329 作者签署之后的任何其他签署（Signed-off-by:'s）均来自处理和传递补丁的人员，但
336 Signed-off-by: 标签表示签名者参与了补丁的开发，或者他/她在补丁的传递路径中。
358 签署程序要求Signed-off-by:标签的顺序应尽可能反映补丁的时间历史，无论作者是通
359 过From:还是Co-developed-by:表明。值得注意的是，最后一个Signed-off-by:必须是
369 Signed-off-by: First Co-Author <first@coauthor.example.org>
371 Signed-off-by: Second Co-Author <second@coauthor.example.org>
372 Signed-off-by: From Author <from@author.example.org>
381 Signed-off-by: Random Co-Author <random@coauthor.example.org>
[all …]
H A D5.Posting.rst125 - 一个或多个标记行，至少有一个由补丁作者的 Signed-off-by 签名。标记将在下面
159 - Signed-off-by: 这是一个开发人员的证明，证明他或她有权提交补丁以包含到内核
167 的Signed-off-by之后。具体内容和示例见以下文件
H A D3.Early-stage.rst113 谁会在这些补丁上加上Signed-off-by行签名（如有）。这些人将是帮助新开发项目的
H A Dresearcher-guidelines.rst119 Signed-off-by: Author <author@email>
/linux/Documentation/translations/zh_CN/maintainer/
H A Dmodifying-patches.rst20 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>
H A Dpull-requests.rst104 Signed-off-by: Your-name-here <your_email@domain>
/linux/Documentation/translations/ja_JP/
H A DSubmittingPatches349 Signed-off-by: Random J Developer <random@developer.example.org>
365 Signed-off-by とあなたがその末尾に追加する Signed-off-by の間に、修正を
371 Signed-off-by: Random J Developer <random@developer.example.org>
373 Signed-off-by: Lucky K Maintainer <lucky@maintainer.example.org>
403 「 Signed-off-by: 」タグはその署名者がパッチの開発に関わっていたことやパッチ
413 Acked-by: は Signed-off-by: のように公式なタグではありません。それはメンテナが
509 - 上述した「 Signed-off-by: 」行。これも説明本体と同じくチェン
/linux/Documentation/process/
H A Dcoding-assistants.rst27 Signed-off-by and Developer Certificate of Origin
30 AI agents MUST NOT add Signed-off-by tags. Only humans can legally
36 * Adding their own Signed-off-by tag to certify the DCO
H A Dsubmitting-patches.rst438 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
477 Acked-by: is not as formal as Signed-off-by:. It is a record that the acker
507 followed by a Signed-off-by: of the associated co-author. Standard sign-off
508 procedure applies, i.e. the ordering of Signed-off-by: tags should reflect the
511 Signed-off-by: must always be that of the developer submitting the patch.
521 Signed-off-by: First Co-Author <first@coauthor.example.org>
523 Signed-off-by: Second Co-Author <second@coauthor.example.org>
[all …]
H A Dmaintainer-tip.rst291 Signed-off-by: J.Dev <j.dev@mail>
299 Signed-off-by: J.Dev <j.dev@mail>
315 Signed-off-by: ``Co-author <co-author@mail>``
317 Note, that Co-developed-by and Signed-off-by of the co-author(s) must
320 - Signed-off-by: ``Author <author@mail>``
322 The first Signed-off-by (SOB) after the last Co-developed-by/SOB pair is the
325 - Signed-off-by: ``Patch handler <handler@mail>``
/linux/Documentation/admin-guide/media/
H A Dsi476x.rst137 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
/linux/Documentation/maintainer/
H A Dmodifying-patches.rst13 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>
H A Dconfigure-git.rst8 developers public GPG key. Signed tags can be created by passing
/linux/Documentation/wmi/
H A Dacpi-interface.rst130 ``sint8`` Signed 8-bit integer. 1 byte
132 ``sint16`` Signed 16-bit little endian integer. 2 bytes
134 ``sint32`` Signed 32-bit little endian integer. 4 bytes
136 ``sint64`` Signed 64-bit little endian integer. 8 bytes
/linux/Documentation/input/devices/
H A Diforce-protocol.rst148 04 Level at end of attack. Signed byte.
160 02 Level. Signed byte.
170 02 Magnitude. Signed byte.
171 03 Offset. Signed byte.
/linux/Documentation/translations/it_IT/process/
H A Dsubmitting-patches.rst477 Signed-off-by: Random J Developer <random@developer.example.org>
482 includere "Signed-off-by", se usate ``git revert -s`` questo verrà
489 In seguito al SoB (Signed-off-by:) dell'autore ve ne sono altri da
500 L'etichetta Signed-off-by: indica che il firmatario è stato coinvolto nello
511 Acked-by: non è formale come Signed-off-by:. Questo indica che la persona ha
534 dev'essere seguito immediatamente dal Signed-off-by: del corrispondente
536 l'ordine delle etichette Signed-off-by: dovrebbe riflettere il più possibile
539 l'ultimo Signed-off-by: dev'essere quello di colui che ha sottomesso la patch.
550 Signed-off-by: First Co-Author <first@coauthor.example.org>
552 Signed-off-by: Second Co-Author <second@coauthor.example.org>
[all …]
/linux/Documentation/translations/sp_SP/process/
H A Dsubmitting-patches.rst469 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 …]
/linux/Documentation/scsi/
H A DChangeLog.megaraid182 Signed-off-by: Daniel Drake <dsd@gentoo.org>
207 - Signed-off-by:Andi Kleen <ak@muc.de>
213 - Signed-off-by: Al Viro
219 - Signed-off-by: Domen Puncer <domen@coderock.org>
226 Signed-off-by: Tobias Klauser <tklauser@nuerscht.ch>
227 Signed-off-by: Domen Puncer <domen@coderock.org>
332 Signed-off-by: Adrian Bunk <bunk@stusta.de>
/linux/Documentation/ABI/testing/
H A Dsysfs-class-power-ltc4162l27 Valid values: Signed value in microamps
/linux/Documentation/translations/zh_CN/doc-guide/
H A Dcontributing.rst82 Signed-off-by: Jonathan Corbet <corbet@lwn.net>
/linux/Documentation/admin-guide/
H A Dmodule-signing.rst11 .. - Signed modules and stripping.
244 Signed modules and stripping
251 Signed modules are BRITTLE as the signature is outside of the defined ELF

123