| /linux/drivers/mtd/ubi/ |
| H A D | attach.c | 9 * UBI attaching sub-system.
11 * This sub-system is responsible for attaching MTD devices and it also
14 * The attaching information is represented by a &struct ubi_attach_info'
51 * attaching, such PEBs are put to the @corr list and UBI preserves them.
57 * corruptions and UBI's strategy is as follows (in case of attaching by
88 * @ai: attaching information
152 * ubi_find_or_add_av - search for a volume in the attaching information and
154 * @ai: attaching information
169 * @ai: attaching information
197 * @ai: attaching information
[all …]
|
| H A D | vtbl.c | 34 * eraseblocks became bad for some reasons. Suppose we are attaching the
278 * @ai: attaching information
327 * And add it to the attaching information. Don't delete the old version in create_vtbl()
354 * @ai: attaching information
355 * @av: layout volume attaching information
479 * @ai: attaching information
667 * check_av - check volume attaching information.
669 * @av: volume attaching information
671 * This function returns zero if the volume attaching information is consistent
702 ubi_err(vol->ubi, "bad attaching information, error %d", err); in check_av()
[all …]
|
| H A D | Kconfig | 53 attaching a partition.
67 Fastmap is a mechanism which allows attaching an UBI device
72 attaching by scanning takes long. UBI will not automatically install
|
| H A D | ubi-media.h | 142 * also contain this value, and will check the value when attaching the flash.
145 * complete, UBI will detect the error when attaching the media.
389 /* 5% of the total number of PEBs have to be scanned while attaching
443 * struct ubi_fm_scan_pool - Fastmap pool PEBs to be scanned while attaching
|
| H A D | ubi.h | 672 * attaching an MTD device. Note, if this PEB does not belong to any LEB /
690 * struct ubi_ainf_volume - attaching information about a volume.
707 * One object of this type is allocated for each volume when attaching an MTD
724 * struct ubi_attach_info - MTD device attaching information.
755 * This data structure contains the result of attaching an MTD device and may
1052 * @av: volume attaching information
1053 * @aeb: attaching eraseblock information
|
| /linux/tools/perf/tests/ |
| H A D | event-times.c | 27 pr_debug("attaching to spawned child, enable on exec\n"); in attach__enable_on_exec()
65 pr_debug("attaching to current thread as disabled\n"); in attach__current_disabled()
91 pr_debug("attaching to current thread as enabled\n"); in attach__current_enabled()
118 pr_debug("attaching to CPU 0 as enabled\n"); in attach__cpu_disabled()
147 pr_debug("attaching to CPU 0 as enabled\n"); in attach__cpu_enabled()
|
| /linux/tools/testing/selftests/bpf/benchs/ |
| H A D | bench_local_storage_rcu_tasks_trace.c | 170 fprintf(stderr, "Error attaching bpf program\n"); in local_storage_tasks_trace_setup()
175 fprintf(stderr, "Error attaching bpf program\n"); in local_storage_tasks_trace_setup()
180 fprintf(stderr, "Error attaching bpf program\n"); in local_storage_tasks_trace_setup()
250 * This benchmark uses both approaches, attaching to rcu_tasks_trace_pregp_step
|
| H A D | bench_local_storage_create.c | 94 fprintf(stderr, "Error attaching bpf program\n"); in setup()
99 fprintf(stderr, "Error attaching bpf program\n"); in setup()
105 fprintf(stderr, "Error attaching bpf program\n"); in setup()
|
| /linux/tools/testing/selftests/bpf/prog_tests/ |
| H A D | cgroup1_hierarchy.c | 20 /* LSM prog will be triggered when attaching fentry */ in bpf_cgroup1()
38 /* LSM prog will be triggered when attaching fentry */ in bpf_cgroup1_sleepable()
56 /* LSM prog will be triggered when attaching fentry */ in bpf_cgroup1_invalid_id()
|
| H A D | xdp_bonding.c | 410 /* attaching to slave when master has no program is allowed */ in test_xdp_bonding_attach()
415 /* attaching to master not allowed when slave has program loaded */ in test_xdp_bonding_attach()
423 /* attaching XDP program to master allowed when slave has no program */ in test_xdp_bonding_attach()
428 /* attaching to slave not allowed when master has program loaded */ in test_xdp_bonding_attach()
445 /* attaching not allowed when one slave does not support XDP */ in test_xdp_bonding_attach()
|
| H A D | flow_dissector_reattach.c | 3 * Tests for attaching, detaching, and replacing flow_dissector BPF program.
101 /* Expect success when attaching a different program */ in test_prog_attach_prog_attach()
109 /* Expect failure when attaching the same program twice */ in test_prog_attach_prog_attach()
186 /* Expect failure attaching prog when link exists */ in test_link_create_prog_attach()
|
| /linux/arch/um/drivers/ |
| H A D | Kconfig | 26 This option enables support for attaching UML consoles and serial
33 This option enables support for attaching UML consoles and serial
43 This option enables support for attaching UML consoles and serial
53 This option enables support for attaching UML consoles and serial
62 This option enables support for attaching UML consoles and serial
|
| /linux/Documentation/i2c/ |
| H A D | old-module-parameters.rst | 26 Attaching a driver to an I2C device
39 Preventing a driver from attaching to an I2C device
|
| /linux/drivers/gpu/drm/tidss/ |
| H A D | tidss_encoder.c | 104 /* Attaching first bridge to the encoder */ in tidss_encoder_create()
121 dev_err(tidss->dev, "attaching encoder to connector failed\n"); in tidss_encoder_create()
|
| /linux/drivers/net/ethernet/chelsio/cxgb4/ |
| H A D | t4_pci_id_tbl.h | 47 * -- for drivers attaching to PF0-3, "4" for drivers attaching to PF4,
48 * -- "8" for drivers attaching to SR-IOV Virtual Functions, etc.
|
| /linux/Documentation/admin-guide/ |
| H A D | bootconfig.rst | 161 There are two options to boot the kernel with bootconfig: attaching the
164 Attaching a Boot Config to Initrd
221 Just as when attaching the bootconfig to the initrd, you need ``bootconfig``
|
| /linux/Documentation/driver-api/ |
| H A D | men-chameleon-bus.rst | 19 4.2 Probing and attaching
145 Probing and attaching
|
| /linux/tools/testing/selftests/bpf/progs/ |
| H A D | fentry_recursive_target.c | 18 /* Dummy bpf prog for testing attach_btf presence when attaching an fentry
|
| /linux/include/rv/ |
| H A D | instrumentation.h | 20 "fail attaching " #monitor " " #tp "handler"); \
|
| /linux/net/netfilter/ |
| H A D | xt_comment.c | 3 * Implements a dummy match to allow attaching comments to rules
|
| /linux/Documentation/devicetree/bindings/gpio/ |
| H A D | gpio-mm-lantiq.txt | 3 By attaching hardware latches to the EBU it is possible to create output
|
| /linux/Documentation/userspace-api/ |
| H A D | iommufd.rst | 99 allows userspace to initiate the attaching operation. If a compatible
128 attaching a device to an IOAS object. This is compatible to the semantics of
|
| /linux/drivers/net/mctp/ |
| H A D | Kconfig | 13 MCTP Serial Transport Binding". By attaching the ldisc to a serial
|
| /linux/tools/testing/selftests/sched_ext/ |
| H A D | enq_last_no_enq_fails.c | 35 SCX_ERR("Incorrectly failed at attaching scheduler"); in run()
|
| /linux/Documentation/devicetree/ |
| H A D | of_unittest.rst | 200 Figure 3: Live device tree structure after attaching the testcase-data.
204 sibling compared to the earlier structure (Figure 2). After attaching first
|