Searched full:linking (Results 1 – 25 of 312) sorted by relevance
12345678910>>...13
| /linux-6.12.1/tools/testing/selftests/drivers/net/netdevsim/ |
| D | peer.sh | 62 # linking
80 echo "linking with non-existent netdevsim should fail"
87 echo "linking with non-existent netnsid should fail"
94 echo "linking with self should fail"
101 echo "linking netdevsim1 with netdevsim2 should succeed"
|
| /linux-6.12.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-6.12.1/tools/perf/Documentation/ |
| D | Build.txt | 43 Those objects are then used in final linking:
82 Below is the command for building the perf with dynamic linking.
87 For static linking, the option `LDFLAGS="-static"` is required.
|
| /linux-6.12.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-6.12.1/Documentation/arch/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-6.12.1/arch/riscv/kernel/tests/ |
| D | Kconfig.debug | 16 bool "KUnit test riscv module linking at runtime" if !KUNIT_ALL_TESTS
20 Enable this option to test riscv module linking at boot. This will
|
| /linux-6.12.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-6.12.1/Documentation/kbuild/ |
| D | kbuild.rst | 80 Additional options used for $(LD) when linking modules.
96 Additional flags to be passed when linking host programs.
110 Additional options used for $(LD) when linking userprogs. userprogs are linked
279 symbols in the final module linking stage. It changes such errors
|
| /linux-6.12.1/scripts/ |
| D | link-vmlinux.sh | 91 # The kallsyms linking does not need debug symbols included.
212 # The kallsyms linking does not need debug symbols, but the BTF does.
254 # The kallsyms linking does not need debug symbols included.
|
| /linux-6.12.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-6.12.1/include/asm-generic/ |
| D | module.lds.h | 6 * <asm/module.lds.h> can specify arch-specific sections for linking modules.
|
| /linux-6.12.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-6.12.1/Documentation/devicetree/bindings/sound/ |
| D | rt274.txt | 16 Pins on the device (for linking into audio routes) for RT274:
|
| D | tda7419.txt | 15 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-6.12.1/tools/testing/selftests/x86/ |
| D | Makefile | 45 # clang only wants to see -no-pie during linking. Here, we don't have a separate
46 # linking stage, so a compiler warning is unavoidable without (wastefully)
|
| /linux-6.12.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-6.12.1/tools/testing/nvdimm/ |
| D | watermark.h | 14 * dummy routine for nfit_test to validate it is linking to the properly
|
| /linux-6.12.1/tools/testing/cxl/ |
| D | watermark.h | 15 * dummy routine for cxl_test to validate it is linking to the properly
|
| /linux-6.12.1/Documentation/userspace-api/ |
| D | landlock.rst | 236 relevant when we want to allow linking or renaming. Indeed, having consistent
539 File renaming and linking (ABI < 2)
547 their hierarchy, moving or linking a file from one directory to another implies
550 escalations through renaming or linking, and for the sake of simplicity,
551 Landlock previously limited linking and renaming to the same directory.
553 control renaming and linking thanks to the new ``LANDLOCK_ACCESS_FS_REFER``
|
| /linux-6.12.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-6.12.1/lib/vdso/ |
| D | Makefile | 10 # It has to be called after the linking of the vdso library and requires it
|
| /linux-6.12.1/LICENSES/exceptions/ |
| D | GCC-exception-2.0 | 6 allow linking the compiled version of code to non GPL compliant code.
|
| /linux-6.12.1/tools/perf/tests/shell/coresight/thread_loop/ |
| D | Makefile | 7 # Any linking/libraries needed for the binary - empty if none needed
|
12345678910>>...13