| /linux/arch/arm/kernel/ |
| H A D | stacktrace.c | 20 * 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 D | messy-diffstat.rst | 12 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/Documentation/iio/ |
| H A D | bno055.rst | 31 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
|
| /linux/tools/testing/selftests/bpf/prog_tests/ |
| H A D | recursive_attach.c | 14 * 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 D | am335x-osd335x-common.dtsi | 26 * 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 D | main.c | 41 * 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/scripts/ |
| H A D | rustdoc_test_builder.rs | 27 // 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/tools/testing/selftests/bpf/ |
| H A D | README.rst | 127 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/Documentation/core-api/ |
| H A D | entry.rst | 64 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:
|
| /linux/drivers/input/keyboard/ |
| H A D | ipaq-micro-keys.c | 32 KEY_ADDRESSBOOK, /* 3: Contacts (looks like Outlook) */
34 KEY_HOMEPAGE, /* 5: Start (looks like swoopy arrow) */
|
| /linux/arch/m68k/mac/ |
| H A D | oss.c | 50 /* 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 D | cache.json | 15 "PublicDescription": "This event counts any load or store operation or page table walk access which looks up in the L1 data cache. In particular, any access which could count the L1D_CACHE_REFILL event causes this event to count.",
31 "PublicDescription": "This event counts any transaction from L1 which looks up in the L2 cache, and any write-back from the L1 to the L2. Snoops from outside the core and cache maintenance operations are not counted.",
|
| /linux/tools/testing/radix-tree/ |
| H A D | regression1.c | 17 * 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/tools/testing/selftests/kvm/x86/ |
| H A D | vmx_nested_tsc_scaling_test.c | 87 /* check that L1's frequency looks alright before launching L2 */ in l1_guest_code()
113 /* check that L1's frequency still looks good */ in l1_guest_code()
|
| /linux/Documentation/ABI/stable/ |
| H A D | sysfs-driver-qla2xxx | 4 Description: qla2xxx-udev.sh currently looks for uevent CHANGE events to
|
| H A D | o2cb | 5 Description: Ocfs2-tools looks at 'interface-revision' for versioning
|
| /linux/Documentation/ABI/obsolete/ |
| H A D | o2cb | 5 Description: Ocfs2-tools looks at 'interface-revision' for versioning
|
| /linux/Documentation/networking/ |
| H A D | phy-link-topology.rst | 17 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/arch/arm/mach-rpc/include/mach/ |
| H A D | io.h | 23 * These peripherals are found in an area of MMIO which looks very much
|
| /linux/tools/include/linux/ |
| H A D | math.h | 5 * This looks more complex than it should be. But we need to
|
| /linux/include/asm-generic/ |
| H A D | uaccess.h | 70 if (0) /* make sure the label looks used to the compiler */ \
77 if (0) /* make sure the label looks used to the compiler */ \
|
| /linux/drivers/pinctrl/aspeed/ |
| H A D | pinctrl-aspeed.c | 345 * - 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/Documentation/filesystems/ |
| H A D | sharedsubtree.rst | 722 the new tree now looks like this::
742 the new tree now looks like this::
804 the new tree now looks like this::
820 the new tree now looks like this::
836 the new tree now looks like this::
896 A example propagation tree looks as shown in the figure below.
897 [ NOTE: Though it looks like a forest, if we consider all the shared
|
| /linux/sound/hda/core/ext/ |
| H A D | stream.c | 337 * coupled: Looks for an unused stream
338 * host: Looks for an unused decoupled host stream
339 * link: Looks for an unused decoupled link stream
|
| /linux/Documentation/ABI/testing/ |
| H A D | procfs-smaps_rollup | 17 Typical output looks like this::
|