Home
last modified time | relevance | path

Searched refs:macros (Results 1 – 25 of 226) sorted by relevance

12345678910

/linux/tools/bpf/bpftool/Documentation/ !
H A Dbpftool-feature.rst26 | **bpftool** **feature probe** [*COMPONENT*] [**full**] [**unprivileged**] [**macros** [**prefix** *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/rust/ !
H A DMakefile44 libmacros_name := $(shell MAKEFLAGS= $(RUSTC) --print file-names --crate-name macros --crate-type p…
99 rustdoc: rustdoc-core rustdoc-macros rustdoc-compiler_builtins \
111 rustdoc-macros: private rustdoc_host = yes
112 rustdoc-macros: private rustc_target_flags = --crate-type proc-macro \
114 rustdoc-macros: $(src)/macros/lib.rs rustdoc-clean FORCE
139 --extern macros --extern alloc --cfg kernel --cfg feature=\"alloc\"
/linux/Documentation/core-api/ !
H A Dasm-annotations.rst6 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
54 As one might realize, there were only three macros previously. That is indeed
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
[all...]
H A Dboot-time-mm.rst16 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/ !
H A Dcputopology.rst12 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/rust/kernel/ !
H A Dtracepoint.rs22 $crate::macros::paste! {
32 $crate::macros::paste! {
H A Dprelude.rs25 pub use macros::{export, kunit_tests, module, vtable};
/linux/Documentation/userspace-api/media/ !
H A Dmedia.h.rst.exceptions6 # Ignore macros
15 #ignore legacy entity type macros
H A Dlirc.h.rst.exceptions6 # Ignore helper macros
73 # Undocumented macros
/linux/Documentation/translations/zh_TW/admin-guide/ !
H A Dcputopology.rst36 ``**_id macros`` 的類型是int。
37 ``**_cpumask macros`` 的類型是 ``(const) struct cpumask *`` 。後者和恰當的
/linux/Documentation/translations/zh_CN/admin-guide/ !
H A Dcputopology.rst36 ``**_id macros`` 的类型是int。
37 ``**_cpumask macros`` 的类型是 ``(const) struct cpumask *`` 。后者和恰当的
/linux/Documentation/arch/powerpc/ !
H A Dcpu_features.rst38 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/rust/kernel/drm/ !
H A Dioctl.rs110 let cmd: u32 = $crate::macros::concat_idents!(DRM_IOCTL_, $cmd);
120 cmd: $crate::macros::concat_idents!(DRM_IOCTL_, $cmd) as u32,
/linux/Documentation/input/ !
H A Duserio.rst30 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
/linux/scripts/coccinelle/tests/ !
H A Dunsigned_lesser_than_zero.cocci10 /// signed functions/macros,
11 /// - hardcoded list of signed functions/macros with always non-negative
/linux/rust/pin-init/src/ !
H A Dmacros.rs3 //! This module provides the macros that actually implement the proc-macros `pin_data` and
5 //! `{try_}{pin_}init!` macros.
7 //! These macros should never be called directly, since they expect their input to be
8 //! in a certain format which is internal. If used incorrectly, these macros can lead to UB even in
9 //! safe code! Use the public facing macros instead.
12 //! would make matters a lot easier for implementing these as proc-macros.
19 //! This section is intended for readers trying to understand the macros in this module and the
20 //! `[try_][pin_]init!` macros from `lib.rs`.
63 //! general things we need to take into account when designing macros
[all...]
/linux/ !
H A D.clippy.toml7 disallowed-macros = [
/linux/tools/memory-model/ !
H A Dlinux-kernel.cfg1 macros linux-kernel.def
/linux/samples/rust/ !
H A DKconfig45 tristate "Printing macros"
47 This option builds the Rust printing macros sample.
/linux/Documentation/devicetree/bindings/pinctrl/ !
H A Dfsl,imx27-pinctrl.txt90 For convenience there are macros defined in imx27-pinfunc.h which provide PIN
94 The above example using macros:
/linux/tools/virtio/asm/ !
H A Dbarrier.h30 #error Please fill in barrier macros
/linux/drivers/gpu/nova-core/regs/ !
H A Dmacros.rs280 ::kernel::macros::paste!(
292 ::kernel::macros::paste!(
301 ::kernel::macros::paste!(
/linux/arch/riscv/boot/dts/renesas/ !
H A Dr9a07g043f01-smarc.dts15 * Please change below macros according to SW1 setting on the SoM
/linux/Documentation/devicetree/bindings/power/ !
H A Dactions,owl-sps.txt9 See macros in:
/linux/Documentation/rust/ !
H A Dtesting.rst115 macros from the Rust standard library (``core``). We provide a custom version
116 that forwards the call to KUnit instead. Importantly, these macros do not
168 Like documentation tests, the ``assert!`` and ``assert_eq!`` macros are mapped
214 Currently, they are mostly used for testing the ``macros`` crate's examples.

12345678910