Home
last modified time | relevance | path

Searched full:looks (Results 1 – 25 of 2176) sorted by relevance

12345678910>>...88

/kernel/linux/linux-6.6/scripts/mod/
Dfile2alias.c168 /* Looks like "usb:vNpNdNdcNdscNdpNicNiscNipNinN" */
399 /* Looks like: hid:bNvNpN */
417 /* Looks like: ieee1394:venNmoNspNverN */
441 /* Looks like: pci:vNdNsvNsdNbcNscNiN or <prefix>_pci:vNdNsvNsdNbcNscNiN. */
497 /* looks like: "ccw:tNmNdtNdmN" */
520 /* looks like: "ap:tN" */
530 /* looks like: "css:tN" */
540 /* Looks like: "serio:tyNprNidNexN" */
559 /* looks like: "acpi:ACPI0003" or "acpi:PNP0C0B" or "acpi:LNXVIDEO" or
596 /* looks like: "pnp:dD" */
[all …]
/kernel/linux/linux-5.10/scripts/mod/
Dfile2alias.c156 /* Looks like "usb:vNpNdNdcNdscNdpNicNiscNipNinN" */
387 /* Looks like: hid:bNvNpN */
405 /* Looks like: ieee1394:venNmoNspNverN */
429 /* Looks like: pci:vNdNsvNsdNbcNscNiN. */
472 /* looks like: "ccw:tNmNdtNdmN" */
495 /* looks like: "ap:tN" */
505 /* looks like: "css:tN" */
515 /* Looks like: "serio:tyNprNidNexN" */
534 /* looks like: "acpi:ACPI0003" or "acpi:PNP0C0B" or "acpi:LNXVIDEO" or
571 /* looks like: "pnp:dD" */
[all …]
/kernel/linux/linux-5.10/arch/s390/kernel/
Dftrace.c25 * The mcount code looks like this:
32 * The enabled ftrace code block looks like this:
44 * The disabled ftrace code block looks like this:
52 * function prologue contains only a single six byte instruction and looks
55 * To enable ftrace the code gets patched like above and afterwards looks
/kernel/linux/linux-5.10/arch/arm/kernel/
Dstacktrace.c17 * With framepointer enabled, a simple function prologue looks like this:
22 * A simple function epilogue looks like this:
26 * prologue looks like this when built with clang:
32 * A simple function epilogue looks like this when built with clang:
/kernel/linux/linux-6.6/arch/arm/kernel/
Dstacktrace.c20 * With framepointer enabled, a simple function prologue looks like this:
25 * A simple function epilogue looks like this:
29 * prologue looks like this when built with clang:
35 * A simple function epilogue looks like this when built with clang:
/kernel/linux/linux-5.10/tools/testing/selftests/bpf/
DREADME.rst14 The symptom looks like
55 The symptom for ``bpf_iter/ipv6_route`` looks like
67 The symptom for ``bpf_iter/netlink`` looks like
/kernel/linux/linux-6.6/Documentation/maintainer/
Dmessy-diffstat.rst12 great deal of unrelated work. The result looks ugly and obscures what the
21 manner, mainline kernel development looks like this::
36 result in the simplest case is a history that looks like::
/kernel/linux/linux-6.6/Documentation/iio/
Dbno055.rst31 the driver looks for at probe time. If found, then the IMU is initialized
36 The driver looks for calibration data file using two different names: first
/kernel/linux/linux-6.6/arch/um/include/asm/
Duaccess.h51 if (0) /* make sure the label looks used to the compiler */ \
58 if (0) /* make sure the label looks used to the compiler */ \
/kernel/linux/linux-6.6/arch/arm/boot/dts/ti/omap/
Dam335x-osd335x-common.dtsi26 * Therefore, from a DEVICE_ID revision point of view, the silicon looks
28 * the HW OPP table, the silicon looks like it is Revision 1.0 (ie the
/kernel/linux/linux-5.10/arch/arm/boot/dts/
Dam335x-osd335x-common.dtsi26 * Therefore, from a DEVICE_ID revision point of view, the silicon looks
28 * the HW OPP table, the silicon looks like it is Revision 1.0 (ie the
/kernel/linux/linux-6.6/tools/testing/selftests/bpf/
DREADME.rst97 The symptom looks like
139 The symptom for ``bpf_iter/ipv6_route`` looks like
151 The symptom for ``bpf_iter/netlink`` looks like
176 The verifier output looks like
245 Without it, the error from compiling bpf selftests looks like:
/kernel/linux/linux-6.6/drivers/base/firmware_loader/builtin/
Dmain.c41 * This looks for the firmware in the built-in kernel. Only if the kernel was
78 * This looks for the firmware in the built-in kernel. Only if the kernel was
/kernel/linux/linux-6.6/scripts/
Drustdoc_test_builder.rs27 // The line we are looking for looks like one of the following: in main()
60 // We save the result in a variable so that the failed assertion message looks nicer. in main()
/kernel/linux/linux-5.10/arch/arm/nwfpe/
Dentry.S52 3) If an instruction has been emulated successfully, it looks ahead at
55 way it repeatedly looks ahead and executes floating point instructions
/kernel/linux/linux-6.6/Documentation/core-api/
Dentry.rst64 invoked from low-level assembly code looks like this:
144 The architecture-specific part looks similar to syscall handling:
229 Architecture-specific code looks like this:
/kernel/linux/linux-5.10/arch/m68k/mac/
Doss.c48 /* Disable all interrupts. Unlike a VIA it looks like we */ in oss_init()
123 * It looks messy but it's rather straightforward. The switch() statement
/kernel/linux/linux-6.6/arch/m68k/mac/
Doss.c48 /* Disable all interrupts. Unlike a VIA it looks like we */ in oss_init()
123 * It looks messy but it's rather straightforward. The switch() statement
/kernel/linux/linux-6.6/drivers/input/keyboard/
Dipaq-micro-keys.c32 KEY_ADDRESSBOOK, /* 3: Contacts (looks like Outlook) */
34 KEY_HOMEPAGE, /* 5: Start (looks like swoopy arrow) */
/kernel/linux/linux-6.6/tools/perf/pmu-events/arch/arm64/arm/cortex-a76/
Dcache.json15 … event counts any load or store operation or page table walk access which looks up in the L1 data …
31 …"PublicDescription": "This event counts any transaction from L1 which looks up in the L2 cache, an…
/kernel/linux/linux-5.10/drivers/input/keyboard/
Dipaq-micro-keys.c32 KEY_ADDRESSBOOK, /* 3: Contacts (looks like Outlook) */
34 KEY_HOMEPAGE, /* 5: Start (looks like swoopy arrow) */
/kernel/linux/linux-6.6/tools/testing/radix-tree/
Dregression1.c17 * 4. The reader looks at the index 0 slot, and finds that the page has 0 ref
19 * 5. The reader looks at it again, hoping that the item will either be freed
/kernel/linux/linux-5.10/tools/testing/radix-tree/
Dregression1.c17 * 4. The reader looks at the index 0 slot, and finds that the page has 0 ref
19 * 5. The reader looks at it again, hoping that the item will either be freed
/kernel/linux/linux-5.10/Documentation/ABI/stable/
Dsysfs-driver-qla2xxx4 Description: qla2xxx-udev.sh currently looks for uevent CHANGE events to
/kernel/linux/linux-6.6/Documentation/ABI/stable/
Dsysfs-driver-qla2xxx4 Description: qla2xxx-udev.sh currently looks for uevent CHANGE events to

12345678910>>...88