| /OK3568_Linux_fs/kernel/Documentation/translations/ja_JP/ |
| H A 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 …]
|
| /OK3568_Linux_fs/app/forlinx/flapp/src/keyboard/pinyin/include/ |
| H A D | matrixsearch.h | 43 // If this node is for composing phrase, this bit is 1. 111 // phrase will be the first lemma in the sentence. Because it contains some 220 // Composing phrase 224 // composing phrase (And definitely it will match successfully). If it 272 // the fixed lemmas into the composing phrase. 320 // Extend dmi for the composing phrase. 413 // composing phrase, clear_fixed_this_step indicates whether we needs to
|
| /OK3568_Linux_fs/app/forlinx/DWKeyboard/include/pinyin/include/ |
| H A D | matrixsearch.h | 43 // If this node is for composing phrase, this bit is 1. 111 // phrase will be the first lemma in the sentence. Because it contains some 220 // Composing phrase 224 // composing phrase (And definitely it will match successfully). If it 272 // the fixed lemmas into the composing phrase. 320 // Extend dmi for the composing phrase. 413 // composing phrase, clear_fixed_this_step indicates whether we needs to
|
| /OK3568_Linux_fs/kernel/Documentation/process/ |
| H A D | submitting-patches.rst | 558 Subject: [PATCH 001/123] subsystem: summary phrase 587 The ``summary phrase`` in the email's Subject should concisely 589 phrase`` should not be a filename. Do not use the same ``summary 590 phrase`` for every patch in a whole patch series (where a ``patch 593 Bear in mind that the ``summary phrase`` of your email becomes a 595 into the ``git`` changelog. The ``summary phrase`` may later be used in 597 google for the ``summary phrase`` to read discussion regarding that 609 The ``summary phrase`` may be prefixed by tags enclosed in square 610 brackets: "Subject: [PATCH <tag>...] <summary phrase>". The tags are 611 not considered part of the summary phrase, but describe how the patch [all …]
|
| /OK3568_Linux_fs/app/forlinx/flapp/src/keyboard/pinyin/share/ |
| H A D | matrixsearch.cpp | 410 // Extend the composing phrase. in reset_search() 534 size_t c_py_len = 0; // The length of composing phrase's Pinyin in delsearch() 548 // Unlock the last sub lemma in the composing phrase. Because it is not in delsearch() 550 // composing phrase. in delsearch() 576 // The composing phrase is valid, reset all search space, in delsearch() 578 // phrase. in delsearch() 582 // Extend the composing phrase. in delsearch() 591 // Fixd the composing phrase as the first choice. in delsearch() 1025 // If it is for extending composing phrase, it's OK to ignore the 0. in add_char_qwerty() 1057 // If it is not in mode for composing phrase, and the source DMI node in add_char_qwerty() [all …]
|
| /OK3568_Linux_fs/kernel/Documentation/translations/it_IT/process/ |
| H A D | submitting-patches.rst | 683 Subject: [PATCH 001/123] subsystem: summary phrase 713 La ``summary phrase`` nell'oggetto dell'email dovrebbe descrivere brevemente 714 il contenuto della patch. La ``summary phrase`` non dovrebbe essere un nome 715 di file. Non utilizzate la stessa ``summary phrase`` per tutte le patch in 719 Ricordatevi che la ``summary phrase`` della vostra email diventerà un 721 changelog ``git``. La ``summary phrase`` potrà essere usata in futuro 723 cercare la ``summary phrase`` su internet per leggere le discussioni che la 733 La ``summary phrase`` può avere un'etichetta (*tag*) di prefisso racchiusa fra 734 le parentesi quadre "Subject: [PATCH <tag>...] <summary phrase>". 768 che la vostra patch venga trovata. Come nella ``summary phrase``, è importante
|
| /OK3568_Linux_fs/yocto/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 | 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 | FreeBSD-DOC | 19 … In the following statement, the phrase "this text" refers to portions of the system documentation.
|
| H A D | iMatix | 17 …3. Add this phrase to the documentation for your product: "This product uses parts of the iMatix S…
|
| /OK3568_Linux_fs/kernel/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 | xlnx,zynq-pinctrl.txt | 10 phrase "pin configuration node".
|
| H A D | qcom,ipq8064-pinctrl.txt | 24 phrase "pin configuration node".
|
| H A D | qcom,apq8064-pinctrl.txt | 24 phrase "pin configuration node".
|
| H A D | qcom,ipq4019-pinctrl.txt | 27 phrase "pin configuration node".
|
| H A D | qcom,msm8660-pinctrl.txt | 24 phrase "pin configuration node".
|
| H A D | brcm,bcm2835-gpio.txt | 37 phrase "pin configuration node".
|
| /OK3568_Linux_fs/buildroot/package/pinentry/ |
| H A D | Config.in | 12 A collection of simple PIN or pass-phrase entry dialogs
|
| /OK3568_Linux_fs/external/security/rk_tee_user/v2/host/openssl/include/openssl/ |
| H A D | ui.h | 179 * textual short description of the object, for example "pass phrase", 190 * So, if object_desc has the value "pass phrase" and object_name has 193 * "Enter pass phrase for foo.key:"
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/arm-none-linux-gnueabihf/libc/usr/include/ |
| H A D | crypt.h | 31 /* One-way hash PHRASE, returning a string suitable for storage in the
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/aarch64-none-linux-gnu/libc/usr/include/ |
| H A D | crypt.h | 31 /* One-way hash PHRASE, returning a string suitable for storage in the
|
| /OK3568_Linux_fs/yocto/poky/meta/recipes-support/curl/curl/ |
| H A D | CVE-2022-27782-2.patch | 64 const char *passphrase; /* pass-phrase to use */
|