Searched full:phrase (Results 1 – 25 of 66) sorted by relevance
123
| /Linux-v5.15/Documentation/translations/ja_JP/ |
| D | SubmittingPatches | 471 Subject: [PATCH 001/123] subsystem: summary phrase
499 電子メールのサブジェクトの「summary phrase」はそのパッチの概要を正確
500 に表現しなければなりません。「summary phrase」をファイル名にしてはい
501 けません。パッチシリーズ中でそれぞれのパッチは同じ「summary phrase」を
505 あなたの電子メールの「summary phrase」がそのパッチにとって世界で唯一の識別子に
506 なるように心がけてください。「summary phrase」は git のチェンジログの中へ
507 ずっと伝播していきます。「summary phrase」は、開発者が後でパッチを参照する
509 人々はそのパッチに関連した議論を読むために「summary phrase」を使って google で
514 これらの理由のため、「summary phrase」はなぜパッチが必要であるか、パッチが何を
516 「summary phrase」は簡潔であり説明的である表現を目指しつつ、うまく
[all …]
|
| /Linux-v5.15/Documentation/process/ |
| D | submitting-patches.rst | 580 Subject: [PATCH 001/123] subsystem: summary phrase
609 The ``summary phrase`` in the email's Subject should concisely
611 phrase`` should not be a filename. Do not use the same ``summary
612 phrase`` for every patch in a whole patch series (where a ``patch
615 Bear in mind that the ``summary phrase`` of your email becomes a
617 into the ``git`` changelog. The ``summary phrase`` may later be used in
619 google for the ``summary phrase`` to read discussion regarding that
631 The ``summary phrase`` may be prefixed by tags enclosed in square
632 brackets: "Subject: [PATCH <tag>...] <summary phrase>". The tags are
633 not considered part of the summary phrase, but describe how the patch
[all …]
|
| /Linux-v5.15/Documentation/translations/it_IT/process/ |
| D | submitting-patches.rst | 607 Subject: [PATCH 001/123] subsystem: summary phrase
637 La ``summary phrase`` nell'oggetto dell'email dovrebbe descrivere brevemente
638 il contenuto della patch. La ``summary phrase`` non dovrebbe essere un nome
639 di file. Non utilizzate la stessa ``summary phrase`` per tutte le patch in
643 Ricordatevi che la ``summary phrase`` della vostra email diventerà un
645 changelog ``git``. La ``summary phrase`` potrà essere usata in futuro
647 cercare la ``summary phrase`` su internet per leggere le discussioni che la
657 La ``summary phrase`` può avere un'etichetta (*tag*) di prefisso racchiusa fra
658 le parentesi quadre "Subject: [PATCH <tag>...] <summary phrase>".
701 venga trovata. Come nella ``summary phrase``, è importante essere sia
|
| /Linux-v5.15/Documentation/devicetree/bindings/pinctrl/ |
| D | marvell,mvebu-pinctrl.txt | 9 phrase "pin configuration node".
|
| D | pinctrl-rk805.txt | 7 including the meaning of the phrase "pin configuration node".
|
| D | pinctrl-vt8500.txt | 21 phrase "pin configuration node".
|
| D | lantiq,pinctrl-falcon.txt | 10 phrase "pin configuration node".
|
| D | qcom,msm8660-pinctrl.txt | 24 phrase "pin configuration node".
|
| D | qcom,apq8064-pinctrl.txt | 24 phrase "pin configuration node".
|
| D | qcom,ipq4019-pinctrl.txt | 27 phrase "pin configuration node".
|
| D | qcom,ipq8064-pinctrl.txt | 24 phrase "pin configuration node".
|
| D | brcm,bcm2835-gpio.txt | 37 phrase "pin configuration node".
|
| D | fsl,imx-pinctrl.txt | 12 phrase "pin configuration node".
|
| D | nvidia,tegra194-pinmux.txt | 11 phrase "pin configuration node".
|
| D | rockchip,pinctrl.txt | 10 phrase "pin configuration node".
|
| D | pinctrl-palmas.txt | 14 phrase "pin configuration node".
|
| D | qcom,msm8974-pinctrl.txt | 24 phrase "pin configuration node".
|
| D | pinctrl-max77620.txt | 8 including the meaning of the phrase "pin configuration node".
|
| D | marvell,armada-37xx-pinctrl.txt | 18 of the phrase "pin configuration node".
|
| D | qcom,mdm9615-pinctrl.txt | 56 phrase "pin configuration node".
|
| D | bitmain,bm1880-pinctrl.txt | 12 phrase "pin configuration node".
|
| D | ste,nomadik.txt | 12 phrase "pin configuration node".
|
| D | ingenic,pinctrl.yaml | 12 phrase "pin configuration node".
|
| D | qcom,apq8084-pinctrl.txt | 56 phrase "pin configuration node".
|
| D | qcom,ipq8074-pinctrl.txt | 56 phrase "pin configuration node".
|
123
