Searched full:phrase (Results 1 – 25 of 42) sorted by relevance
12
| /linux-6.14.4/Documentation/translations/ja_JP/ |
| 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 …]
|
| /linux-6.14.4/Documentation/process/ |
| D | submitting-patches.rst | 636 Subject: [PATCH 001/123] subsystem: summary phrase
665 The ``summary phrase`` in the email's Subject should concisely
667 phrase`` should not be a filename. Do not use the same ``summary
668 phrase`` for every patch in a whole patch series (where a ``patch
671 Bear in mind that the ``summary phrase`` of your email becomes a
673 into the ``git`` changelog. The ``summary phrase`` may later be used in
675 google for the ``summary phrase`` to read discussion regarding that
687 The ``summary phrase`` may be prefixed by tags enclosed in square
688 brackets: "Subject: [PATCH <tag>...] <summary phrase>". The tags are
689 not considered part of the summary phrase, but describe how the patch
[all …]
|
| /linux-6.14.4/Documentation/translations/it_IT/process/ |
| D | submitting-patches.rst | 661 Subject: [PATCH 001/123] subsystem: summary phrase
691 La ``summary phrase`` nell'oggetto dell'email dovrebbe descrivere brevemente
692 il contenuto della patch. La ``summary phrase`` non dovrebbe essere un nome
693 di file. Non utilizzate la stessa ``summary phrase`` per tutte le patch in
697 Ricordatevi che la ``summary phrase`` della vostra email diventerà un
699 changelog ``git``. La ``summary phrase`` potrà essere usata in futuro
701 cercare la ``summary phrase`` su internet per leggere le discussioni che la
711 La ``summary phrase`` può avere un'etichetta (*tag*) di prefisso racchiusa fra
712 le parentesi quadre "Subject: [PATCH <tag>...] <summary phrase>".
755 venga trovata. Come nella ``summary phrase``, è importante essere sia
|
| /linux-6.14.4/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 | brcm,bcm2835-gpio.txt | 37 phrase "pin configuration node".
|
| D | fsl,imx-pinctrl.txt | 12 phrase "pin configuration node".
|
| D | pinctrl-palmas.txt | 14 phrase "pin configuration node".
|
| D | marvell,armada-37xx-pinctrl.txt | 18 of the phrase "pin configuration node".
|
| D | pinctrl-max77620.txt | 8 including the meaning of the phrase "pin configuration node".
|
| D | ingenic,pinctrl.yaml | 12 phrase "pin configuration node".
|
| D | rockchip,pinctrl.yaml | 20 phrase "pin configuration node".
|
| D | ste,nomadik.txt | 12 phrase "pin configuration node".
|
| D | bitmain,bm1880-pinctrl.txt | 12 phrase "pin configuration node".
|
| D | ste,abx500.txt | 9 phrase "pin configuration node".
|
| D | xlnx,pinctrl-zynq.yaml | 15 phrase "pin configuration node".
|
| D | actions,s700-pinctrl.txt | 29 phrase "pin configuration node".
|
| D | lantiq,pinctrl-xway.txt | 15 phrase "pin configuration node".
|
| D | nvidia,tegra-pinmux-common.yaml | 16 the phrase "pin configuration node".
|
| D | actions,s900-pinctrl.txt | 29 phrase "pin configuration node".
|
| /linux-6.14.4/Documentation/devicetree/bindings/mfd/ |
| D | as3722.txt | 36 phrase "pin configuration node".
|
| /linux-6.14.4/include/sound/sof/ |
| D | topology.h | 36 SOF_COMP_KPB, /* A key phrase buffer component */
|
| /linux-6.14.4/Documentation/sphinx/ |
| D | kerneldoc-preamble.sty | 201 \xeCJKsetup{CJKspace = true}% For inter-phrase space of Korean TOC
|
12