| /Linux-v4.19/fs/btrfs/ |
| D | extent_map.c | 228 struct extent_map *merge = NULL; in try_merge_map() local
234 merge = rb_entry(rb, struct extent_map, rb_node); in try_merge_map()
235 if (rb && mergable_maps(merge, em)) { in try_merge_map()
236 em->start = merge->start; in try_merge_map()
237 em->orig_start = merge->orig_start; in try_merge_map()
238 em->len += merge->len; in try_merge_map()
239 em->block_len += merge->block_len; in try_merge_map()
240 em->block_start = merge->block_start; in try_merge_map()
241 em->mod_len = (em->mod_len + em->mod_start) - merge->mod_start; in try_merge_map()
242 em->mod_start = merge->mod_start; in try_merge_map()
[all …]
|
| /Linux-v4.19/Documentation/device-mapper/ |
| D | snapshot.txt | 11 *) To merge a snapshot of a block device back into the snapshot's origin
18 For snapshot merge the contents of the COW storage are merged back into
23 snapshot, snapshot-origin, and snapshot-merge.
53 snapshot-origin or snapshot-merge target must be suspended. A failure to
57 * snapshot-merge <origin> <COW device> <persistent> <chunksize>
67 has started (in the background) the <origin> may be opened and the merge
107 How snapshot-merge is used by LVM2
111 "snapshot-merge". The "-real" device is not changed and the "-cow"
114 COW device to the "snapshot-merge" is deactivated (unless using lvchange
117 A snapshot will merge into its origin with the following command:
[all …]
|
| /Linux-v4.19/fs/notify/ |
| D | notification.c | 99 int (*merge)(struct list_head *, in fsnotify_add_event()
126 if (!list_empty(list) && merge) { in fsnotify_add_event()
127 ret = merge(list, event); in fsnotify_add_event()
|
| /Linux-v4.19/lib/ |
| D | list_sort.c | 17 static struct list_head *merge(void *priv, in merge() function
126 cur = merge(priv, cmp, part[lev], cur); in list_sort()
141 list = merge(priv, cmp, part[lev], list); in list_sort()
|
| /Linux-v4.19/Documentation/block/ |
| D | deadline-iosched.txt | 63 request, or it fits at the front. That is called either a back merge candidate
64 or a front merge candidate. Due to the way files are typically laid out,
67 front merge requests. Setting front_merges to 0 disables this functionality.
70 rbtree front sector lookup when the io scheduler merge function is called.
|
| /Linux-v4.19/Documentation/media/kapi/ |
| D | v4l2-event.rst | 58 ``merge()`` and ``replace()`` callbacks which drivers can set. These
67 The ``merge()`` callback allows you to merge the oldest event payload into
74 A good example of these ``replace``/``merge`` callbacks is in v4l2-event.c:
120 merge merge event 'old' into event 'new'.
|
| /Linux-v4.19/arch/x86/pci/ |
| D | bus_numa.c | 96 resource_size_t end, unsigned long flags, int merge) in update_res() argument
107 if (!merge) in update_res()
|
| D | bus_numa.h | 26 resource_size_t end, unsigned long flags, int merge);
|
| /Linux-v4.19/Documentation/maintainer/ |
| D | pull-requests.rst | 53 itself, and then in the merge commit that the maintainer makes if/when they
54 merge the pull request. So write it up well, as it will be in the kernel
61 want to use that message as the message for the merge, so it should
69 suspicious. And when you send me new stuff after the merge window
72 happened that this didn't go through the merge window..
85 it right now), but may not make sense in the context of a merge
97 Here is the big char/misc patch set for the 4.15-rc1 merge window.
|
| /Linux-v4.19/drivers/staging/rtl8192e/ |
| D | TODO | 1 * merge into drivers/net/wireless/rtllib/rtl8192e
|
| /Linux-v4.19/Documentation/ABI/testing/ |
| D | sysfs-block-dm | 32 reasonable merge candidate can be queued on the request
36 request-based DM's merge heuristic and associated extra
|
| /Linux-v4.19/kernel/gcov/ |
| D | gcc_3_4.c | 56 void (*merge)(gcov_type *, unsigned int); member
271 dup->counts[i].merge = ctr->merge; in gcov_info_dup()
|
| /Linux-v4.19/Documentation/process/ |
| D | 2.Process.rst | 37 cycle, the "merge window" is said to be open. At that time, code which is
45 merge window do not come out of thin air; they have been collected, tested,
49 The merge window lasts for approximately two weeks. At the end of this
52 for example, the release which happens at the end of the merge window will
54 merge new features has passed, and that the time to stabilize the next
59 allowed, but such occasions are rare; developers who try to merge new
60 features outside of the merge window tend to get an unfriendly reception.
61 As a general rule, if you miss the merge window for a given feature, the
78 February 11 4.16-rc1, merge window closes
100 worse; the pile of changes waiting for the next merge window will grow
[all …]
|
| D | 7.AdvancedTopics.rst | 65 Publicly-available branches should be created with care; merge in patches
92 you try to push changes which do not result in a fast-forward merge
102 advances, it is tempting to merge with that tree to stay on the leading
105 world. Once that happens, a full merge must be done. Merging occasionally
107 needlessly. Suggested technique in this case is to merge infrequently, and
111 useful in such situations; it remembers how merge conflicts were resolved
|
| /Linux-v4.19/drivers/dma/ |
| D | TODO | 11 4. Check other subsystems for dma drivers and merge/move to dmaengine
|
| /Linux-v4.19/drivers/media/v4l2-core/ |
| D | v4l2-event.c | 134 } else if (sev->ops && sev->ops->merge) { in __v4l2_event_queue_fh()
137 sev->ops->merge(&kev->event, &second_oldest->event); in __v4l2_event_queue_fh()
340 .merge = v4l2_event_src_merge,
|
| /Linux-v4.19/drivers/staging/rtl8712/ |
| D | TODO | 2 - merge Realtek's bugfixes and new features into the driver
|
| /Linux-v4.19/drivers/staging/rtlwifi/ |
| D | TODO | 7 - merge Realtek's bugfixes and new features into the driver
|
| /Linux-v4.19/drivers/staging/vt6656/ |
| D | TODO | 5 - prepare for merge with vt6655 driver:
|
| /Linux-v4.19/drivers/staging/vt6655/ |
| D | TODO | 3 - prepare for merge with vt6656 driver:
|
| /Linux-v4.19/drivers/staging/rtl8188eu/ |
| D | TODO | 9 - merge Realtek's bugfixes and new features into the driver
|
| /Linux-v4.19/include/media/ |
| D | v4l2-event.h | 56 void (*merge)(const struct v4l2_event *old, struct v4l2_event *new); member
|
| /Linux-v4.19/drivers/staging/rtl8723bs/ |
| D | TODO | 10 - merge Realtek's bugfixes and new features into the driver
|
| /Linux-v4.19/Documentation/devicetree/bindings/display/mediatek/ |
| D | mediatek,disp.txt | 36 "mediatek,<chip>-disp-merge" - merge streams from two RDMA sources
46 merge and split function blocks).
|
| /Linux-v4.19/Documentation/translations/zh_CN/video4linux/ |
| D | v4l2-framework.txt | 912 此外，v4l2_subscribed_event 结构体内部有可供驱动设置的 merge() 和
916 kevent 结构体时，它将被调用。merge() 回调让你可以合并最早的事件净荷
923 关于 replace/merge 回调的一个不错的例子在 v4l2-event.c 中：用于
950 * merge: 将‘早期‘事件合并到‘新’事件中。
|
