| /linux/samples/rust/ |
| H A D | rust_minimal.rs | 16 numbers: KVec<i32>, field
24 let mut numbers = KVec::new(); in init() localVariable
25 numbers.push(72, GFP_KERNEL)?; in init()
26 numbers.push(108, GFP_KERNEL)?; in init()
27 numbers.push(200, GFP_KERNEL)?; in init()
29 Ok(RustMinimal { numbers }) in init()
35 pr_info!("My numbers are {:?}\n", self.numbers); in drop()
|
| /linux/Documentation/staging/ |
| H A D | magic-number.rst | 3 Linux magic numbers
6 This file is a registry of magic numbers which are in use. When you
8 file, since it is best if the magic numbers used by various structures
12 numbers. This allows you to check at run time whether (a) a structure
19 The way to use magic numbers is to declare them at the beginning of
54 but it is possible that some new magic numbers will sneak into the
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-stm | 6 Shows first and last available to software master numbers on
21 Reads as 0 if master numbers in the STP stream produced by
22 this stm device will match the master numbers assigned by
|
| H A D | configfs-stp-policy | 39 Write two numbers: the first master and the last master number.
46 Write two numbers: the first channel and the last channel
|
| /linux/arch/powerpc/boot/dts/ |
| H A D | currituck.dts | 149 * We are de-swizzling here because the numbers are actually for
151 * to avoid putting a node for it in the tree, so the numbers
152 * below are basically de-swizzled numbers.
186 * We are de-swizzling here because the numbers are actually for
188 * to avoid putting a node for it in the tree, so the numbers
189 * below are basically de-swizzled numbers.
223 * We are de-swizzling here because the numbers are actually for
225 * to avoid putting a node for it in the tree, so the numbers
226 * below are basically de-swizzled numbers.
|
| H A D | akebono.dts | 277 * We are de-swizzling here because the numbers are actually for
279 * to avoid putting a node for it in the tree, so the numbers
280 * below are basically de-swizzled numbers.
317 * We are de-swizzling here because the numbers are actually for
319 * to avoid putting a node for it in the tree, so the numbers
320 * below are basically de-swizzled numbers.
357 * We are de-swizzling here because the numbers are actually for
359 * to avoid putting a node for it in the tree, so the numbers
360 * below are basically de-swizzled numbers.
397 * We are de-swizzling here because the numbers ar
[all...] |
| H A D | redwood.dts | 265 * We are de-swizzling here because the numbers are actually for
267 * to avoid putting a node for it in the tree, so the numbers
268 * below are basically de-swizzled numbers.
306 * We are de-swizzling here because the numbers are actually for
308 * to avoid putting a node for it in the tree, so the numbers
309 * below are basically de-swizzled numbers.
347 * We are de-swizzling here because the numbers are actually for
349 * to avoid putting a node for it in the tree, so the numbers
350 * below are basically de-swizzled numbers.
|
| H A D | katmai.dts | 349 * We are de-swizzling here because the numbers are actually for
351 * to avoid putting a node for it in the tree, so the numbers
352 * below are basically de-swizzled numbers.
390 * We are de-swizzling here because the numbers are actually for
392 * to avoid putting a node for it in the tree, so the numbers
393 * below are basically de-swizzled numbers.
431 * We are de-swizzling here because the numbers are actually for
433 * to avoid putting a node for it in the tree, so the numbers
434 * below are basically de-swizzled numbers.
|
| /linux/Documentation/core-api/irq/ |
| H A D | irq-domain.rst | 10 IRQ numbers.
18 So in the past, IRQ numbers could be chosen so that they match the
22 correspondence to hardware interrupt numbers.
25 interrupt numbers, called hardware IRQs, from Linux IRQ numbers.
28 IRQ numbers, but they don't provide any support for reverse mapping of
32 The irq_domain library adds a mapping between hwirq and IRQ numbers on
38 irq_fwspec to hwirq numbers (Device Tree, non-DT firmware node, ACPI
47 numbers for a given interrupt domain. The domain structure is
68 between hwirq and IRQ numbers
[all...] |
| /linux/kernel/ |
| H A D | pid.c | 58 .numbers = { {
101 ns = pid->numbers[pid->level].ns; in put_pid()
124 struct upid *upid = pid->numbers + i; in free_pid()
248 pid->numbers[i].nr = nr; in alloc_pid()
249 pid->numbers[i].ns = tmp; in alloc_pid()
272 upid = pid->numbers + ns->level; in alloc_pid()
278 for ( ; upid >= pid->numbers; --upid) { in alloc_pid()
296 upid = pid->numbers + i; in alloc_pid()
495 upid = &pid->numbers[ns->level]; in pid_nr_ns()
812 struct_size_t(struct pid, numbers, in pid_idr_init()
[all...] |
| /linux/Documentation/driver-api/cxl/platform/acpi/ |
| H A D | srat.rst | 51 bridge. With the association, latency and bandwidth numbers can be retrieved
68 Proximity Domain List for the related latency or bandwidth numbers. Those
69 performance numbers are tied to a CXL host bridge via the Device Handle.
71 numbers for the whole CXL path access coordinates calculation.
|
| /linux/include/linux/ |
| H A D | pid.h | 73 struct upid numbers[]; member
153 ns = pid->numbers[pid->level].ns; in ns_of_pid()
165 return pid->numbers[pid->level].nr == 1; in is_child_reaper()
183 nr = pid->numbers[0].nr; in pid_nr()
|
| /linux/sound/ |
| H A D | Kconfig | 16 bool "Preclaim OSS device numbers"
21 numbers if any OSS support (native or emulation) is enabled
24 module aliases when one of the device numbers is opened. With
26 device numbers and opening a missing device will generate only the
|
| /linux/lib/tests/ |
| H A D | scanf_kunit.c | 144 /* Selection of interesting numbers to test, copied from test-kstrtox.c */
145 static const unsigned long long numbers[] = { variable
192 for (i = 0; i < ARRAY_SIZE(numbers); i++) { \
193 if (value_representable_in_type(T, numbers[i])) \
195 numbers[i], fn); \
197 if (value_representable_in_type(T, -numbers[i])) \
199 -numbers[i], fn); \
278 * Define a pattern of negative and positive numbers to ensure we get
509 * List of numbers separated by delim. Each field width specifier is the
575 * List of numbers separate
[all...] |
| /linux/Documentation/devicetree/bindings/soc/fsl/cpm_qe/qe/ |
| H A D | firmware.txt | 15 as an array of two 32-bit numbers.
17 It is an array of 8 32-bit numbers.
|
| /linux/Documentation/usb/ |
| H A D | functionfs.rst | 21 to worry about endpoints, interfaces or strings numbers but
23 only one (endpoints and strings numbers starting from one and
24 interface numbers starting from zero). The FunctionFS changes
25 them as needed also handling situation when numbers differ in
33 numbers and changing of the configuration (which means that
|
| /linux/Documentation/i2c/muxes/ |
| H A D | i2c-mux-gpio.rst | 69 If you don't know the absolute GPIO pin numbers at registration time,
71 numbers, and the i2c-mux-gpio driver will do the work for you,
85 GPIO pin numbers at registration time, this is even the only option.
|
| /linux/Documentation/virt/kvm/arm/ |
| H A D | hypercalls.rst | 34 | Return Values: | (uint32) | R0 | Bitmap of available function numbers 0-31 |
36 | | (uint32) | R1 | Bitmap of available function numbers 32-63 |
38 | | (uint32) | R2 | Bitmap of available function numbers 64-95 |
40 | | (uint32) | R3 | Bitmap of available function numbers 96-127 |
|
| /linux/Documentation/devicetree/bindings/sound/ |
| H A D | omap-mcbsp.txt | 12 - interrupts: Interrupt numbers for the McBSP port, as an array in case the
17 - interrupt-names: Array of strings associated with the interrupt numbers
|
| /linux/Documentation/arch/powerpc/ |
| H A D | vcpudispatch_stats.rst | 23 a vcpu as represented by the first field, followed by 8 numbers.
29 The next 4 numbers represent vcpu dispatch dispersions:
39 The final 3 numbers represent statistics in relation to the home node of
|
| H A D | associativity.rst | 31 The “ibm,associativity” property contains a list of one or more numbers (domainID)
34 The “ibm,associativity-reference-points” property contains a list of one or more numbers
59 "ibm,numa-lookup-index-table" property contains a list of one or more numbers representing
71 "ibm,numa-distance-table" property contains a list of one or more numbers representing the NUMA
|
| /linux/Documentation/devicetree/bindings/usb/ |
| H A D | twlxxxx-usb.txt | 5 - interrupts : Two interrupt numbers to the cpu should be specified. First
25 - interrupts : The interrupt numbers to the cpu should be specified. First
|
| /linux/Documentation/devicetree/bindings/bus/ |
| H A D | brcm,bus-axi.txt | 12 BCM47xx/BCM53xx ARM SoCs. To assign IRQ numbers to the cores, provide
19 detected (e.g. IRQ numbers). Also some of the cores may be responsible
|
| /linux/Documentation/arch/arm/sa1100/ |
| H A D | serial_uart.rst | 5 The SA1100 serial port had its major/minor numbers officially assigned::
13 > Okay. Note that device numbers 204 and 205 are used for "low density
|
| /linux/tools/net/sunrpc/xdrgen/templates/C/program/definition/ |
| H A D | open.j2 | 4 /* procedure numbers for {{ program }} */
|