Home
last modified time | relevance | path

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

12345678910>>...36

/linux/scripts/mod/
H A Dfile2alias.c182 /* Looks like "usb:vNpNdNdcNdscNdpNicNiscNipNinN" */ in do_usb_entry()
379 /* Looks like: hid:bNvNpN */ in do_hid_entry()
397 /* Looks like: ieee1394:venNmoNspNverN */ in do_ieee1394_entry()
420 /* Looks like: pci:vNdNsvNsdNbcNscNiN or <prefix>_pci:vNdNsvNsdNbcNscNiN. */ in do_pci_entry()
475 /* looks like: "ccw:tNmNdtNdmN" */ in do_ccw_entry()
498 /* looks like: "ap:tN" */ in do_ap_entry()
506 /* looks like: "css:tN" */ in do_css_entry()
514 /* Looks like: "serio:tyNprNidNexN" */ in do_serio_entry()
532 /* looks like: "acpi:ACPI0003" or "acpi:PNP0C0B" or "acpi:LNXVIDEO" or
566 /* looks lik
[all...]
/linux/arch/arm/kernel/
H A 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:
/linux/Documentation/maintainer/
H A 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::
/linux/tools/testing/selftests/bpf/prog_tests/
H A Drecursive_attach.c14 * detach = false). The chain looks like this:
20 * chain looks like this:
29 * detached. The chain looks like this:
/linux/arch/arm/boot/dts/ti/omap/
H A 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
/linux/drivers/base/firmware_loader/builtin/
H A 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
/linux/tools/testing/selftests/bpf/
H A DREADME.rst127 The symptom looks like
169 The symptom for ``bpf_iter/ipv6_route`` looks like
181 The symptom for ``bpf_iter/netlink`` looks like
206 The verifier output looks like
275 Without it, the error from compiling bpf selftests looks like:
/linux/scripts/
H A Drustdoc_test_builder.rs27 // The line we are looking for looks like one of the following: in main()
62 // We save the result in a variable so that the failed assertion message looks nicer. in main()
/linux/arch/m68k/mac/
H A Doss.c50 /* Disable all interrupts. Unlike a VIA it looks like we */ in oss_init()
125 * It looks messy but it's rather straightforward. The switch() statement
/linux/tools/perf/pmu-events/arch/arm64/arm/cortex-a76/
H A 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…
/linux/tools/testing/radix-tree/
H A 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
/linux/Documentation/networking/
H A Dphy-link-topology.rst17 when designing these configuration APIs were that the link looks something like ::
35 The link topology then looks like this (when an SFP module is inserted) ::
/linux/Documentation/ABI/stable/
H A Dsysfs-driver-qla2xxx4 Description: qla2xxx-udev.sh currently looks for uevent CHANGE events to
H A Do2cb5 Description: Ocfs2-tools looks at 'interface-revision' for versioning
/linux/Documentation/ABI/obsolete/
H A Do2cb5 Description: Ocfs2-tools looks at 'interface-revision' for versioning
/linux/drivers/pinctrl/aspeed/
H A Dpinctrl-aspeed.c345 * - expr->signal looks like "GPIOD0" in aspeed_expr_is_gpio()
346 * - expr->function looks like "GPIOD0" in aspeed_expr_is_gpio()
349 * - expr->signal looks like "GPIOD1" in aspeed_expr_is_gpio()
350 * - expr->function looks like "GPIOD1" in aspeed_expr_is_gpio()
/linux/arch/arm/nwfpe/
H A 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
/linux/include/asm-generic/
H A Duaccess.h70 if (0) /* make sure the label looks used to the compiler */ \
77 if (0) /* make sure the label looks used to the compiler */ \
/linux/sound/hda/core/ext/
H A Dstream.c334 * coupled: Looks for an unused stream
335 * host: Looks for an unused decoupled host stream
336 * link: Looks for an unused decoupled link stream
/linux/arch/arm/mach-rpc/include/mach/
H A Dio.h23 * These peripherals are found in an area of MMIO which looks very much
/linux/tools/include/linux/
H A Dmath.h5 * This looks more complex than it should be. But we need to
/linux/Documentation/devicetree/bindings/display/panel/
H A Dpanel-edp.yaml38 looks the exactly the same as every other panel. Each panel datasheet
81 The above looks fairly complex but, as per above, each panel only cares
/linux/drivers/base/firmware_loader/
H A DKconfig92 looks for the firmware files listed in the EXTRA_FIRMWARE option.
146 looks for and cannot possibly be specified using the firmware_class
/linux/Documentation/ABI/testing/
H A Dprocfs-smaps_rollup17 Typical output looks like this::
/linux/arch/nios2/include/asm/
H A Dpgtable-bits.h15 * which looks like this:

12345678910>>...36