Searched refs:markers (Results 1 – 17 of 17) sorted by relevance
68 struct marker *m = val.markers; in write_propval_string()141 struct marker *m = val.markers; in write_propval_cells()171 struct marker *m = val.markers; in write_propval_bytes()199 struct marker *m = prop->val.markers; in write_propval()
27 m = d.markers; in data_free()145 struct marker **mp = &d.markers; in data_append_markers()157 struct marker *m2 = d2.markers; in data_merge()165 d2.markers = NULL; /* So data_free() doesn't clobber them */ in data_merge()
351 struct marker *m = prop->val.markers; in check_duplicate_label_prop()380 m = prop->val.markers; in check_explicit_phandles()459 struct marker *m = prop->val.markers; in fixup_phandle_references()483 struct marker *m = prop->val.markers; in fixup_path_references()
87 struct marker *markers; member
417 m = p->val.markers; in get_marker_label()
176 struct marker *m = d.markers; in asm_emit_data()
335 unsigned int *markers; in write_src() local377 markers = malloc(sizeof(unsigned int) * ((table_cnt + 255) / 256)); in write_src()378 if (!markers) { in write_src()388 markers[i >> 8] = off; in write_src()401 printf("\tPTR\t%d\n", markers[i]); in write_src()404 free(markers); in write_src()
50 /Module.markers
72 Module.markers
829 indicated with special markers. For example, emacs interprets lines marked842 Vim interprets markers that look like this:848 includes markers for indentation and mode configuration. People may use their
666 Having used these markers, one can later use
63 During tracing you can place comments (markers) into the trace by66 which action. It is recommended to place descriptive markers about what you
731 markers883 markers - When set, the trace_marker is writable (only by root).
22 time-consuming - having to insert TRACE_RESUME() markers into the device
334 entire flash looking for bad block markers.
27 - Used as markers to separate events. Events may be separated in time or in
428 * Fix sparse warnings by adding __iomem markers to lpfc_compat.h.