Searched refs:macros (Results 1 – 25 of 284) sorted by relevance
12345678910>>...12
| /linux/rust/ |
| A D | Makefile | 83 rustdoc: rustdoc-core rustdoc-macros rustdoc-compiler_builtins \
95 rustdoc-macros: private rustdoc_host = yes
98 rustdoc-macros: $(src)/macros/lib.rs FORCE
120 rustdoc-kernel: $(src)/kernel/lib.rs rustdoc-core rustdoc-macros \
139 rusttestlib-macros: private rustc_test_library_proc = yes
140 rusttestlib-macros: $(src)/macros/lib.rs FORCE
166 --extern build_error --extern macros \
193 rusttest: rusttest-macros rusttest-kernel
195 rusttest-macros: private rustc_target_flags = --extern proc_macro
197 rusttest-macros: $(src)/macros/lib.rs FORCE
[all …]
|
| /linux/tools/bpf/bpftool/Documentation/ |
| A D | bpftool-feature.rst | 26 | **bpftool** **feature probe** [*COMPONENT*] [**full**] [**unprivileged**] [**macros** [**prefix**…
35 bpftool feature probe [kernel] [full] [macros [prefix *PREFIX*]]
44 If the **macros** keyword (but not the **-j** option) is passed, a subset
45 of the output is dumped as a list of **#define** macros that are ready to
48 to the names of the macros: this can be used to avoid conflicts on macro
62 bpftool feature probe dev *NAME* [full] [macros [prefix *PREFIX*]]
66 The keywords **full**, **macros** and **prefix** have the same role as when
|
| /linux/Documentation/core-api/ |
| A D | asm-annotations.rst | 6 This document describes the new macros for annotation of data and code in
21 Over time, the Linux kernel has adopted macros from various projects (like
24 annotations in assembly. Due to the lack of their documentation, the macros
31 When these macros are used correctly, they help assemblers generate a nice
62 macros, it was decided that brand new macros should be introduced instead::
73 The new macros are prefixed with the ``SYM_`` prefix and can be divided into
125 example, having some asm instructions in between the macros, of course::
132 and ``ENDPROC`` macros.
212 earlier macros, or in ``SYM_START``.
217 Architecture can also override any of the macros in their own
[all …]
|
| A D | boot-time-mm.rst | 16 functions and macros for memory allocations. The allocation request
34 macros. Some of them are actually internal, but since they are
|
| /linux/Documentation/admin-guide/ |
| A D | cputopology.rst | 12 only be created if an architecture provides the related macros as described
16 these macros in include/asm-XXX/topology.h::
31 The type of ``**_id macros`` is int.
32 The type of ``**_cpumask macros`` is ``(const) struct cpumask *``. The latter
37 provides default definitions for any of the above macros that are
|
| /linux/Documentation/devicetree/bindings/clock/ |
| A D | maxim,max77686.txt | 11 (gated/ungated) over I2C. Clocks are defined as preprocessor macros in
16 (gated/ungated) over I2C. Clocks are defined as preprocessor macros in
20 (gated/ungated) over I2C. Clocks are defined as preprocessor macros in
38 Clocks are defined as preprocessor macros in above dt-binding header for
|
| A D | intel,cgu-lgm.yaml | 18 defines all available clocks as macros. These macros can be used in device
|
| A D | rockchip,rk3128-cru.yaml | 19 preprocessor macros in the dt-bindings/clock/rk3128-cru.h headers and can be
20 used in device tree sources. Similar macros exist for the reset sources in
|
| A D | rockchip,rk3036-cru.yaml | 19 preprocessor macros in the dt-bindings/clock/rk3036-cru.h headers and can be
20 used in device tree sources. Similar macros exist for the reset sources in
|
| A D | rockchip,rk3228-cru.yaml | 19 preprocessor macros in the dt-bindings/clock/rk3228-cru.h headers and can be
20 used in device tree sources. Similar macros exist for the reset sources in
|
| A D | rockchip,rk3308-cru.yaml | 19 preprocessor macros in the dt-bindings/clock/rk3308-cru.h headers and can be
20 used in device tree sources. Similar macros exist for the reset sources in
|
| A D | rockchip,rk3328-cru.txt | 22 preprocessor macros in the dt-bindings/clock/rk3328-cru.h headers and can be
23 used in device tree sources. Similar macros exist for the reset sources in
|
| A D | rockchip,rk3188-cru.yaml | 19 preprocessor macros in the dt-bindings/clock/rk3188-cru.h and
21 Similar macros exist for the reset sources in these files.
|
| A D | rockchip,rk3368-cru.yaml | 19 preprocessor macros in the dt-bindings/clock/rk3368-cru.h headers and can be
20 used in device tree sources. Similar macros exist for the reset sources in
|
| A D | rockchip,rv1108-cru.yaml | 19 preprocessor macros in the dt-bindings/clock/rv1108-cru.h headers and can be
20 used in device tree sources. Similar macros exist for the reset sources in
|
| /linux/Documentation/userspace-api/media/ |
| A D | media.h.rst.exceptions | 6 # Ignore macros
15 #ignore legacy entity type macros
|
| A D | lirc.h.rst.exceptions | 6 # Ignore helper macros
73 # Undocumented macros
|
| /linux/samples/rust/ |
| A D | Kconfig | 24 tristate "Printing macros"
26 This option builds the Rust printing macros sample.
|
| /linux/Documentation/devicetree/bindings/clock/sifive/ |
| A D | fu540-prci.yaml | 17 macros defined in include/dt-bindings/clock/sifive-fu540-prci.h.
18 These macros begin with PRCI_CLK_.
|
| A D | fu740-prci.yaml | 18 macros defined in include/dt-bindings/clock/sifive-fu740-prci.h.
19 These macros begin with PRCI_CLK_.
|
| /linux/Documentation/translations/zh_CN/admin-guide/ |
| A D | cputopology.rst | 36 ``**_id macros`` 的类型是int。
37 ``**_cpumask macros`` 的类型是 ``(const) struct cpumask *`` 。后者和恰当的
|
| /linux/Documentation/translations/zh_TW/admin-guide/ |
| A D | cputopology.rst | 36 ``**_id macros`` 的類型是int。
37 ``**_cpumask macros`` 的類型是 ``(const) struct cpumask *`` 。後者和恰當的
|
| /linux/Documentation/arch/powerpc/ |
| A D | cpu_features.rst | 38 just 2 macros (found in arch/powerpc/include/asm/cputable.h), as seen in head.S
53 cur_cpu_spec[0]->cpu_features) or is cleared, respectively. These two macros
56 The END_FTR_SECTION macros are implemented by storing information about this
|
| /linux/Documentation/devicetree/bindings/phy/ |
| A D | microchip,lan966x-serdes.yaml | 20 following macros are defined CU(X), SERDES6G(X), RGMII(X). Where X is a
41 - The macro to be used. The macros are defined in
|
| /linux/Documentation/input/ |
| A D | userio.rst | 30 macros you need to interact with the device are defined in <linux/userio.h> and
44 of the USERIO_CMD macros defined in <linux/userio.h>. ``data`` is the argument
69 set. Can be any of the macros from <linux/serio.h>. For example: SERIO_8042
|
Completed in 31 milliseconds
12345678910>>...12