/openbmc/linux/Documentation/translations/ja_JP/ |
H A D | SubmittingPatches | 472 Subject: [PATCH 001/123] subsystem: summary phrase 500 電子メールのサブジェクトの「summary phrase」はそのパッチの概要を正確 501 に表現しなければなりません。「summary phrase」をファイル名にしてはい 502 けません。パッチシリーズ中でそれぞれのパッチは同じ「summary phrase」を 506 あなたの電子メールの「summary phrase」がそのパッチにとって世界で唯一の識別子に 507 なるように心がけてください。「summary phrase」は git のチェンジログの中へ 508 ずっと伝播していきます。「summary phrase」は、開発者が後でパッチを参照する 510 人々はそのパッチに関連した議論を読むために「summary phrase」を使って google で 515 これらの理由のため、「summary phrase」はなぜパッチが必要であるか、パッチが何を 517 「summary phrase」は簡潔であり説明的である表現を目指しつつ、うまく [all …]
|
/openbmc/qemu/util/ |
H A D | error-report.c | 183 * a single phrase, with no newline or trailing punctuation. 222 * a single phrase, with no newline or trailing punctuation. 234 * a single phrase, with no newline or trailing punctuation. 246 * a single phrase, with no newline or trailing punctuation. 257 * a single phrase, with no newline or trailing punctuation. 273 * single phrase, with no newline or trailing punctuation. 289 * single phrase, with no newline or trailing punctuation.
|
/openbmc/qemu/tests/unit/ |
H A D | test-crypto-pbkdf.c | 116 .salt = "pass phrase equals block size", 131 .salt = "pass phrase exceeds block size", 252 .salt = "pass phrase exceeds block size", 269 .salt = "pass phrase exceeds block size", 286 .salt = "pass phrase exceeds block size", 303 .salt = "pass phrase exceeds block size", 320 .salt = "pass phrase exceeds block size", 352 .salt = "pass phrase exceeds block size",
|
/openbmc/openbmc/meta-security/recipes-security/ecryptfs-utils/files/ |
H A D | ecryptfs-utils-CVE-2016-6224.patch | 10 erroneously prompted to enter a pass-phrase to unlock their swap partition 36 + erroneously prompted to enter a pass-phrase to unlock their swap partition
|
/openbmc/linux/Documentation/process/ |
H A D | submitting-patches.rst | 615 Subject: [PATCH 001/123] subsystem: summary phrase 644 The ``summary phrase`` in the email's Subject should concisely 646 phrase`` should not be a filename. Do not use the same ``summary 647 phrase`` for every patch in a whole patch series (where a ``patch 650 Bear in mind that the ``summary phrase`` of your email becomes a 652 into the ``git`` changelog. The ``summary phrase`` may later be used in 654 google for the ``summary phrase`` to read discussion regarding that 666 The ``summary phrase`` may be prefixed by tags enclosed in square 667 brackets: "Subject: [PATCH <tag>...] <summary phrase>". The tags are 668 not considered part of the summary phrase, but describe how the patch [all …]
|
/openbmc/linux/Documentation/translations/it_IT/process/ |
H A D | submitting-patches.rst | 610 Subject: [PATCH 001/123] subsystem: summary phrase 640 La ``summary phrase`` nell'oggetto dell'email dovrebbe descrivere brevemente 641 il contenuto della patch. La ``summary phrase`` non dovrebbe essere un nome 642 di file. Non utilizzate la stessa ``summary phrase`` per tutte le patch in 646 Ricordatevi che la ``summary phrase`` della vostra email diventerà un 648 changelog ``git``. La ``summary phrase`` potrà essere usata in futuro 650 cercare la ``summary phrase`` su internet per leggere le discussioni che la 660 La ``summary phrase`` può avere un'etichetta (*tag*) di prefisso racchiusa fra 661 le parentesi quadre "Subject: [PATCH <tag>...] <summary phrase>". 704 venga trovata. Come nella ``summary phrase``, è importante essere sia
|
/openbmc/openbmc/poky/meta/files/common-licenses/ |
H A D | OPUBL-1.0 | 55 To accomplish this, add the phrase `Distribution of substantively modified versions of this documen… 59 To accomplish this, add the phrase 'Distribution of the work or derivative of the work in any stand…
|
H A D | FreeBSD-DOC | 19 … In the following statement, the phrase "this text" refers to portions of the system documentation.
|
H A D | CPAL-1.0 | 64 … “Socialtext”, “CPAL” or any confusingly similar phrase do not appear in y… 86 …phrase, graphic image and a URL (“Attribution Information”) and is subject to the Attr… 105 Attribution Phrase (not exceeding 10 words): _______________________
|
H A D | iMatix | 17 …3. Add this phrase to the documentation for your product: "This product uses parts of the iMatix S…
|
H A D | Catharon | 111 We suggest, but do not require, that you use the following phrase
|
/openbmc/linux/Documentation/devicetree/bindings/pinctrl/ |
H A D | marvell,mvebu-pinctrl.txt | 9 phrase "pin configuration node".
|
H A D | pinctrl-rk805.txt | 7 including the meaning of the phrase "pin configuration node".
|
H A D | pinctrl-vt8500.txt | 21 phrase "pin configuration node".
|
H A D | lantiq,pinctrl-falcon.txt | 10 phrase "pin configuration node".
|
H A D | qcom,ipq8064-pinctrl.txt | 24 phrase "pin configuration node".
|
H A D | qcom,ipq4019-pinctrl.txt | 27 phrase "pin configuration node".
|
H A D | qcom,apq8064-pinctrl.txt | 24 phrase "pin configuration node".
|
H A D | brcm,bcm2835-gpio.txt | 37 phrase "pin configuration node".
|
H A D | fsl,imx-pinctrl.txt | 12 phrase "pin configuration node".
|
H A D | pinctrl-palmas.txt | 14 phrase "pin configuration node".
|
H A D | pinctrl-max77620.txt | 8 including the meaning of the phrase "pin configuration node".
|
H A D | marvell,armada-37xx-pinctrl.txt | 18 of the phrase "pin configuration node".
|
H A D | ingenic,pinctrl.yaml | 12 phrase "pin configuration node".
|
/openbmc/u-boot/doc/device-tree-bindings/pinctrl/ |
H A D | marvell,armada-37xx-pinctrl.txt | 13 of the phrase "pin configuration node".
|