Searched full:linking (Results 1 – 25 of 272) sorted by relevance
1234567891011
| /Linux-v6.1/Documentation/driver-api/tty/ |
| D | tty_driver.rst | 70 variants described in `Linking Devices to Ports`_ later. It is up to driver to
86 Linking Devices to Ports
93 This way, the driver needs not care about linking later on.
102 The linking routines are documented here:
|
| /Linux-v6.1/arch/arm64/kvm/hyp/nvhe/ |
| D | hyp.lds.S | 6 * Linker script used for partial linking of nVHE EL2 object files.
22 * alignment for when linking into vmlinux.
|
| /Linux-v6.1/Documentation/arm/keystone/ |
| D | knav-qmss.rst | 12 processors(PDSP), linking RAM, descriptor pools and infrastructure
18 Linking RAM registers are used to link the descriptors which are stored in
20 The QMSS driver manages the PDSP setups, linking RAM regions,
|
| /Linux-v6.1/Documentation/userspace-api/ |
| D | landlock.rst | 175 relevant when we want to allow linking or renaming. Indeed, having consistent
346 As for file renaming and linking, a sandboxed thread cannot modify its
384 File renaming and linking (ABI < 2)
392 their hierarchy, moving or linking a file from one directory to another implies
395 escalations through renaming or linking, and for the sake of simplicity,
396 Landlock previously limited linking and renaming to the same directory.
398 control renaming and linking thanks to the new ``LANDLOCK_ACCESS_FS_REFER``
|
| /Linux-v6.1/Documentation/kbuild/ |
| D | kbuild.rst | 75 Additional options used for $(LD) when linking modules.
91 Additional flags to be passed when linking host programs.
105 Additional options used for $(LD) when linking userprogs. userprogs are linked
257 symbols in the final module linking stage. It changes such errors
|
| /Linux-v6.1/include/linux/ |
| D | zstd_errors.h | 31 * note 1 : this API shall be used with static linking only.
32 * dynamic linking is not yet officially supported.
|
| /Linux-v6.1/Documentation/devicetree/bindings/soc/ti/ |
| D | keystone-navigator-qmss.txt | 6 processors(PDSP), linking RAM, descriptor pools and infrastructure
12 Linking RAM registers are used to link the descriptors which are stored in
14 The QMSS driver manages the PDSP setups, linking RAM regions,
|
| /Linux-v6.1/include/asm-generic/ |
| D | module.lds.h | 6 * <asm/module.lds.h> can specify arch-specific sections for linking modules.
|
| /Linux-v6.1/drivers/net/ethernet/microchip/lan966x/ |
| D | lan966x_switchdev.c | 313 if (info->linking) in lan966x_port_changeupper()
322 if (info->linking) in lan966x_port_changeupper()
340 if (netif_is_bridge_master(info->upper_dev) && !info->linking) { in lan966x_port_prechangeupper()
347 if (err || info->linking) in lan966x_port_prechangeupper()
|
| /Linux-v6.1/Documentation/devicetree/bindings/sound/ |
| D | rt274.txt | 16 Pins on the device (for linking into audio routes) for RT274:
|
| D | rt5616.txt | 17 Pins on the device (for linking into audio routes) for RT5616:
|
| D | wm8753.txt | 13 Pins on the device (for linking into audio routes):
|
| D | wm8904.txt | 12 Pins on the device (for linking into audio routes):
|
| D | rt5631.txt | 11 Pins on the device (for linking into audio routes):
|
| D | tda7419.txt | 15 Pins on the device (for linking into audio routes):
|
| D | rt5514.txt | 23 Pins on the device (for linking into audio routes) for I2C:
|
| D | alc5632.txt | 16 Pins on the device (for linking into audio routes):
|
| D | rt5660.txt | 29 Pins on the device (for linking into audio routes) for RT5660:
|
| /Linux-v6.1/tools/testing/nvdimm/ |
| D | watermark.h | 14 * dummy routine for nfit_test to validate it is linking to the properly
|
| /Linux-v6.1/tools/perf/bench/ |
| D | mem-memset-x86-64-asm.S | 12 * NOT executable stack. Otherwise the final linking will assume that
|
| D | mem-memcpy-x86-64-asm.S | 17 * NOT executable stack. Otherwise the final linking will assume that
|
| /Linux-v6.1/LICENSES/preferred/ |
| D | LGPL-2.1 | 85 libraries in order to permit linking those libraries into non-free
91 License therefore permits such linking only if the entire combination fits
93 criteria for linking other code with the library.
255 However, linking a "work that uses the Library" with the Library creates
305 b) Use a suitable shared library mechanism for linking with the
|
| /Linux-v6.1/lib/vdso/ |
| D | Makefile | 9 # It has to be called after the linking of the vdso library and requires it
|
| /Linux-v6.1/include/uapi/linux/ |
| D | landlock.h | 127 * access right. When linking or renaming a file, the destination directory
131 * set to ``EXDEV``. Linking also requires a ``LANDLOCK_ACCESS_FS_MAKE_*``
|
| /Linux-v6.1/LICENSES/exceptions/ |
| D | GCC-exception-2.0 | 6 allow linking the compiled version of code to non GPL compliant code.
|
1234567891011
