| /Linux-v6.6/fs/nls/ |
| D | Kconfig | 3 # Native language support configuration
7 tristate "Native language support"
9 The base Native Language Support. A number of filesystems
44 native language character sets. These character sets are stored
56 native language character sets. These character sets are stored
68 native language character sets. These character sets are stored
81 native language character sets. These character sets are stored in
97 native language character sets. These character sets are stored in
112 native language character sets. These character sets are stored in
123 native language character sets. These character sets are stored in
[all …]
|
| /Linux-v6.6/Documentation/process/ |
| D | programming-language.rst | 3 Programming Language
6 The kernel is written in the C programming language [c-language]_.
12 This dialect contains many extensions to the language [gnu-extensions]_,
20 implementation-defined semantics to language entities (like variables,
22 to the language (e.g. adding a new keyword) [n2049]_.
37 The kernel has experimental support for the Rust programming language
38 [rust-language]_ under ``CONFIG_RUST``. It is compiled with ``rustc`` [rustc]_
40 small changes to the language that are not backwards compatible.
48 .. [c-language] http://www.open-std.org/jtc1/sc22/wg14/www/standards
55 .. [rust-language] https://www.rust-lang.org
|
| /Linux-v6.6/scripts/kconfig/tests/err_recursive_dep/ |
| D | expected_stderr | 3 For a resolution refer to Documentation/kbuild/kconfig-language.rst
8 For a resolution refer to Documentation/kbuild/kconfig-language.rst
14 For a resolution refer to Documentation/kbuild/kconfig-language.rst
20 For a resolution refer to Documentation/kbuild/kconfig-language.rst
26 For a resolution refer to Documentation/kbuild/kconfig-language.rst
31 For a resolution refer to Documentation/kbuild/kconfig-language.rst
37 For a resolution refer to Documentation/kbuild/kconfig-language.rst
|
| /Linux-v6.6/Documentation/userspace-api/media/v4l/ |
| D | vidioc-g-tuner.rst | 249 - Reception of the primary language of a bilingual audio program is
251 transmitting the primary language monaural on the main audio
252 carrier and a secondary language monaural on a second carrier.
256 - Reception of the secondary language of a bilingual audio program
264 transmissions of a primary language, and an independent third
265 carrier for a monaural secondary language. Only
316 - The tuner receives the primary language of a bilingual audio
321 - The tuner receives the secondary language of a bilingual audio
350 bilingual or SAP signal this mode selects the primary language.
355 primary language is played on both channels.
[all …]
|
| /Linux-v6.6/tools/memory-model/Documentation/ |
| D | access-marking.txt | 17 1. Plain C-language accesses (unmarked), for example, "a = b;"
33 Neither plain C-language accesses nor data_race() (#1 and #2 above) place
40 C-language accesses. It is permissible to combine #2 and #3, for example,
45 C-language accesses, but marking all accesses involved in a given data
54 data_race() and even plain C-language accesses is preferable to
85 concurrently with updates to x. Then using plain C-language writes
95 In theory, plain C-language loads can also be used for this use case.
119 In theory, plain C-language loads can also be used for this use case.
140 In theory, plain C-language loads can also be used for this use case.
156 Plain C-language stores can also be used for this use case. However,
[all …]
|
| D | ordering.txt | 187 Note that smp_wmb() might fail to provide ordering for unmarked C-language
199 Therefore, if you need to use smp_wmb() with unmarked C-language writes,
445 b. Unmarked C-language accesses.
495 Unmarked C-Language Accesses
498 Unmarked C-language accesses are normal variable accesses to normal
502 might (and sometimes does) split a plain C-language store into multiple
507 Unmarked C-language accesses are unordered, and are also subject to
509 concurrent code. It is possible to used unmarked C-language accesses for
514 C-language accesses requires careful attention to not just your code,
520 But there are some ways of using unmarked C-language accesses for shared
[all …]
|
| /Linux-v6.6/drivers/usb/gadget/ |
| D | usbstring.c | 41 /* descriptor 0 has the language id */ in usb_gadget_get_string()
45 buf [2] = (u8) table->language; in usb_gadget_get_string()
46 buf [3] = (u8) (table->language >> 8); in usb_gadget_get_string()
70 * usb_validate_langid - validate usb language identifiers
71 * @langid: usb language identifier
73 * Returns true for valid language identifier, otherwise false.
|
| D | configfs.c | 28 stringtab_dev->language = num; in check_user_usb_string()
858 struct gadget_language *language; in gadget_language_string_make() local
861 language = to_gadget_language(&group->cg_item); in gadget_language_string_make()
867 string->usb_string.id = language->nstrings++; in gadget_language_string_make()
869 list_add_tail(&string->list, &language->gadget_strings); in gadget_language_string_make()
879 struct gadget_language *language; in gadget_language_string_drop() local
883 language = to_gadget_language(&group->cg_item); in gadget_language_string_drop()
887 language->nstrings--; in gadget_language_string_drop()
889 /* Reset the ids for the language's strings to guarantee a continuous set */ in gadget_language_string_drop()
890 list_for_each_entry(string, &language->gadget_strings, list) in gadget_language_string_drop()
[all …]
|
| /Linux-v6.6/Documentation/translations/zh_CN/process/ |
| D | programming-language.rst | 3 :Original: :ref:`Documentation/process/programming-language.rst <programming_language>`
11 内核是用C语言 :ref:`c-language <cn_c-language>` 编写的。更准确地说，内核通常是用 :ref:`gcc <cn_gcc>`
33 .. _cn_c-language:
35 c-language
|
| /Linux-v6.6/Documentation/translations/zh_TW/process/ |
| D | programming-language.rst | 5 :Original: :ref:`Documentation/process/programming-language.rst <programming_language>`
14 內核是用C語言 :ref:`c-language <tw_c-language>` 編寫的。更準確地說，內核通常是用 :ref:`gcc <tw_gcc>`
36 .. _tw_c-language:
38 c-language
|
| /Linux-v6.6/Documentation/kbuild/ |
| D | kconfig-macro-language.rst | 2 Kconfig macro language
9 two languages in one. One language describes dependency graphs consisting of
10 targets and prerequisites. The other is a macro language for performing textual
13 There is clear distinction between the two language stages. For example, you
23 The macro language replaces the variable references with their expanded form,
40 The macro language in Kconfig processes the source file into the following
47 dependency as explained in kconfig-language.rst.
145 Kconfig adopts Make-like macro language, but the function call syntax is
|
| D | issues.rst | 9 :language: kconfig
15 :language: kconfig
|
| D | index.rst | 10 kconfig-language
11 kconfig-macro-language
|
| /Linux-v6.6/Documentation/translations/ |
| D | index.rst | 30 documentation in their native language, but please bear in mind that the
51 one language directly to all other languages. Each language has its own
53 adapted to fit a different language. For this reason, when viewing
|
| /Linux-v6.6/Documentation/translations/it_IT/process/ |
| D | programming-language.rst | 3 :Original: :ref:`Documentation/process/programming-language.rst <programming_language>`
11 Il kernel è scritto nel linguaggio di programmazione C [it-c-language]_.
46 [it-rust-language]_ abilitando l'opzione di configurazione ``CONFIG_RUST``. Il
58 .. [it-c-language] http://www.open-std.org/jtc1/sc22/wg14/www/standards
65 .. [it-rust-language] https://www.rust-lang.org
|
| /Linux-v6.6/Documentation/admin-guide/aoe/ |
| D | examples.rst | 11 :language: shell
17 :language: shell
23 :language: shell
|
| /Linux-v6.6/tools/testing/selftests/rcutorture/bin/ |
| D | mkinitrd.sh | 22 # Create a C-language initrd/init infinite-loop program and statically
24 echo "Creating a statically linked C-language initrd"
85 echo "Failed to create a statically linked C-language initrd"
90 echo "Done creating a statically linked C-language initrd"
|
| /Linux-v6.6/tools/include/asm-generic/ |
| D | bitops.h | 10 * architecture, here are some C-language equivalents. You should
11 * recode these in the native assembly language, if at all possible.
13 * C language equivalents written by Theodore Ts'o, 9/26/92
|
| /Linux-v6.6/include/asm-generic/ |
| D | bitops.h | 7 * architecture, here are some C-language equivalents. They should
9 * out before rolling your own buggy implementation in assembly language.
11 * C language equivalents written by Theodore Ts'o, 9/26/92
|
| /Linux-v6.6/Documentation/translations/sp_SP/process/ |
| D | programming-language.rst | 3 :Original: :ref:`Documentation/process/programming-language.rst <programming_language>`
11 El kernel está escrito en el lenguaje de programación C [sp-c-language]_.
46 .. [sp-c-language] http://www.open-std.org/jtc1/sc22/wg14/www/standards
|
| /Linux-v6.6/Documentation/ABI/testing/ |
| D | configfs-usb-gadget | 55 This group contains subdirectories for language-specific
58 What: /config/usb-gadget/gadget/configs/config/strings/language
118 This group contains subdirectories for language-specific
121 What: /config/usb-gadget/gadget/strings/language
|
| /Linux-v6.6/arch/sparc/kernel/ |
| D | asm-offsets.c | 4 * assembly language modules.
9 * #defines from the assembly-language output.
|
| /Linux-v6.6/tools/power/cpupower/ |
| D | README | 40 libtoolization, the manpages and the italian language file for cpupower;
42 powernow-k8-decode and intel_gsic tools as well as the french language file;
|
| /Linux-v6.6/rust/kernel/ |
| D | static_assert.rs | 11 /// [`_Static_assert`]: https://en.cppreference.com/w/c/language/_Static_assert
12 /// [`static_assert`]: https://en.cppreference.com/w/cpp/language/static_assert
|
| /Linux-v6.6/arch/openrisc/kernel/ |
| D | asm-offsets.c | 14 * assembly language modules.
19 * #defines from the assembly-language output.
|
