| /linux-6.1.9/Documentation/devicetree/bindings/display/mediatek/ |
| D | mediatek,merge.yaml | 4 $id: http://devicetree.org/schemas/display/mediatek/mediatek,merge.yaml#
7 title: Mediatek display merge
14 Mediatek display merge, namely MERGE, is used to merge two slice-per-line
25 - const: mediatek,mt8173-disp-merge
27 - const: mediatek,mt8195-disp-merge
47 - const: merge
49 - const: merge
52 mediatek,merge-fifo-en:
54 The setting of merge fifo is mainly provided for the display latency
57 According to the merge fifo settings, when the water level is detected
[all …]
|
| /linux-6.1.9/Documentation/maintainer/ |
| D | rebasing-and-merging.rst | 16 the kernel community is not scared by seeing merge commits in its
68 newer base or avoiding a merge with an upstream repository is not
84 A frequent cause of merge-window trouble is when Linus is presented with a
98 development cycle included 1,126 merge commits - nearly 9% of the total.
101 independently of the others. So naturally, at least one merge will be
105 current trunk so that no merge commits appear in the history. The kernel
118 on such a pull request will almost certainly generate a merge commit; that
120 the --no-ff flag to force the addition of a merge commit in the rare cases
121 where one would not normally be created so that the reasons for the merge
122 can be recorded. The changelog for the merge should, for any kind of
[all …]
|
| D | maintainer-entry-profile.rst | 54 sent at any time before the merge window closes and can still be
56 be settled in soaking in linux-next in advance of the merge window
62 New feature submissions targeting the next merge window should have
65 the NEXT+1 merge window, or should come with sufficient justification
70 - Last -rc to merge features: Deadline for merge decisions
72 set will need to wait for the NEXT+1 merge window. Of course there is no
75 resubmit for the following merge window.
|
| 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.
|
| D | messy-diffstat.rst | 70 branch or performing another merge with the linus branch, then recreating
76 situation is to indeed to do a merge with the branch you intend your work
78 shame. Create a new, throwaway branch and do the merge there::
86 The merge operation resolves all of the complications resulting from the
|
| D | modifying-patches.rst | 7 modify patches you receive in order to merge them, because the code is not
24 want at the same time to credit the author, track changes, merge the fix,
|
| /linux-6.1.9/fs/btrfs/ |
| D | extent_map.c | 241 struct extent_map *merge = NULL; in try_merge_map() local
258 merge = rb_entry(rb, struct extent_map, rb_node); in try_merge_map()
259 if (rb && mergable_maps(merge, em)) { in try_merge_map()
260 em->start = merge->start; in try_merge_map()
261 em->orig_start = merge->orig_start; in try_merge_map()
262 em->len += merge->len; in try_merge_map()
263 em->block_len += merge->block_len; in try_merge_map()
264 em->block_start = merge->block_start; in try_merge_map()
265 em->mod_len = (em->mod_len + em->mod_start) - merge->mod_start; in try_merge_map()
266 em->mod_start = merge->mod_start; in try_merge_map()
[all …]
|
| /linux-6.1.9/Documentation/admin-guide/device-mapper/ |
| D | snapshot.rst | 12 - To merge a snapshot of a block device back into the snapshot's origin
19 For snapshot merge the contents of the COW storage are merged back into
24 snapshot, snapshot-origin, and snapshot-merge.
55 snapshot-origin or snapshot-merge target must be suspended. A failure to
73 - snapshot-merge <origin> <COW device> <persistent> <chunksize>
84 has started (in the background) the <origin> may be opened and the merge
124 How snapshot-merge is used by LVM2
128 "snapshot-merge". The "-real" device is not changed and the "-cow"
131 COW device to the "snapshot-merge" is deactivated (unless using lvchange
134 A snapshot will merge into its origin with the following command::
[all …]
|
| /linux-6.1.9/drivers/net/ethernet/netronome/nfp/flower/ |
| D | offload.c | 586 struct nfp_flower_merge_check *merge, in nfp_flower_update_merge_with_actions() argument
616 merge->tci = cpu_to_be16(0xffff); in nfp_flower_update_merge_with_actions()
619 merge->tci = cpu_to_be16(0); in nfp_flower_update_merge_with_actions()
623 eth_broadcast_addr(&merge->l2.mac_dst[0]); in nfp_flower_update_merge_with_actions()
624 eth_broadcast_addr(&merge->l2.mac_src[0]); in nfp_flower_update_merge_with_actions()
625 memset(&merge->l4, 0xff, in nfp_flower_update_merge_with_actions()
628 memset(&merge->ipv6, 0xff, in nfp_flower_update_merge_with_actions()
631 memset(&merge->ipv4, 0xff, in nfp_flower_update_merge_with_actions()
637 merge->l2.mac_dst[i] |= eth->eth_addr_mask[i]; in nfp_flower_update_merge_with_actions()
639 merge->l2.mac_src[i] |= in nfp_flower_update_merge_with_actions()
[all …]
|
| /linux-6.1.9/fs/notify/ |
| D | notification.c | 83 int (*merge)(struct fsnotify_group *, in fsnotify_insert_event()
112 if (!list_empty(list) && merge) { in fsnotify_insert_event()
113 ret = merge(group, event); in fsnotify_insert_event()
|
| /linux-6.1.9/tools/lib/ |
| D | list_sort.c | 15 static struct list_head *merge(void *priv, list_cmp_func_t cmp, in merge() function
224 a = merge(priv, cmp, b, a); in list_sort()
246 list = merge(priv, cmp, pending, list); in list_sort()
|
| /linux-6.1.9/lib/ |
| D | list_sort.c | 16 static struct list_head *merge(void *priv, list_cmp_func_t cmp, in merge() function
225 a = merge(priv, cmp, b, a); in list_sort()
247 list = merge(priv, cmp, pending, list); in list_sort()
|
| /linux-6.1.9/tools/perf/tests/shell/ |
| D | stat.sh | 79 if ! perf stat --no-merge -e "$ok_grouping" true > /dev/null 2>&1
85 if perf stat --no-merge -e "$group_needs_break" true 2>&1 | egrep -q "<not supported>"
|
| /linux-6.1.9/Documentation/block/ |
| D | deadline-iosched.rst | 62 request, or it fits at the front. That is called either a back merge candidate
63 or a front merge candidate. Due to the way files are typically laid out,
66 front merge requests. Setting front_merges to 0 disables this functionality.
69 rbtree front sector lookup when the io scheduler merge function is called.
|
| /linux-6.1.9/Documentation/driver-api/media/ |
| D | v4l2-event.rst | 59 ``merge()`` and ``replace()`` callbacks which drivers can set. These
68 The ``merge()`` callback allows you to merge the oldest event payload into
75 A good example of these ``replace``/``merge`` callbacks is in v4l2-event.c:
121 merge merge event 'old' into event 'new'.
|
| /linux-6.1.9/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-6.1.9/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-6.1.9/drivers/staging/rtl8192e/ |
| D | TODO | 1 * merge into drivers/net/wireless/rtllib/rtl8192e
|
| /linux-6.1.9/tools/testing/selftests/bpf/ |
| D | DENYLIST | 2 get_stack_raw_tp # spams with kernel warnings until next bpf -> bpf-next merge
|
| /linux-6.1.9/Documentation/doc-guide/ |
| D | maintainer-profile.rst | 34 the merge window. The docs tree tends to close late before the merge
|
| /linux-6.1.9/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 September 30 5.4-rc1, merge window closes
101 worse; the pile of changes waiting for the next merge window will grow
[all …]
|
| /linux-6.1.9/Documentation/translations/zh_CN/maintainer/ |
| D | rebasing-and-merging.rst | 159 git merge v5.2-rc1^0
|
| /linux-6.1.9/arch/powerpc/include/asm/ |
| D | kexec_ranges.h | 7 void sort_memory_ranges(struct crash_mem *mrngs, bool merge);
|
| /linux-6.1.9/drivers/dma/ |
| D | TODO | 11 4. Check other subsystems for dma drivers and merge/move to dmaengine
|