Home
last modified time | relevance | path

Searched full:immortal (Results 1 – 12 of 12) sorted by relevance

/linux-6.12.1/arch/powerpc/kernel/
Dudbg.c167 if (strstr(boot_command_line, "udbg-immortal")) { in register_early_udbg_console()
168 printk(KERN_INFO "early console immortal !\n"); in register_early_udbg_console()
/linux-6.12.1/Documentation/devicetree/bindings/phy/
Dphy-rockchip-usbdp.yaml34 - const: immortal
137 clock-names = "refclk", "immortal", "pclk", "utmi";
/linux-6.12.1/arch/powerpc/boot/dts/
Dgamecube.dts19 bootargs = "root=/dev/gcnsda2 rootwait udbg-immortal";
Dwii.dts29 bootargs = "root=/dev/mmcblk0p2 rootwait udbg-immortal";
/linux-6.12.1/arch/arm64/boot/dts/rockchip/
Drk3588-extra.dtsi406 clock-names = "refclk", "immortal", "pclk", "utmi";
Drk3588-base.dtsi2792 clock-names = "refclk", "immortal", "pclk", "utmi";
/linux-6.12.1/kernel/rcu/
Dtree_plugin.h1160 * The ->boost_kthread_task is immortal, so we don't need to worry
/linux-6.12.1/net/netfilter/
DKconfig909 since you can easily create immortal packets that loop
/linux-6.12.1/lib/
Ddynamic_debug.c1250 * immortal. For loaded modules, name points at the name[] in ddebug_add_module()
/linux-6.12.1/Documentation/security/keys/
Dcore.rst65 instantiation function. Keys can also be immortal.
/linux-6.12.1/Documentation/RCU/
DRTFP.txt123 of inside-out reference counts is that they can be stored in immortal
/linux-6.12.1/Documentation/admin-guide/
Dkernel-parameters.txt7085 udbg-immortal [PPC] When debugging early kernel crashes that