Home
last modified time | relevance | path

Searched full:merge (Results 1 – 25 of 3233) sorted by relevance

12345678910>>...130

/Linux-v6.6/Documentation/devicetree/bindings/display/mediatek/
Dmediatek,merge.yaml4 $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
16 MERGE device node must be siblings to the central MMSYS_CONFIG node.
25 - mediatek,mt8173-disp-merge
26 - mediatek,mt8195-disp-merge
28 - const: mediatek,mt6795-disp-merge
29 - const: mediatek,mt8173-disp-merge
49 - const: merge
51 - const: merge
[all …]
/Linux-v6.6/Documentation/maintainer/
Drebasing-and-merging.rst16 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 …]
Dmaintainer-entry-profile.rst54 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.
Dpull-requests.rst51 itself, and then in the merge commit that the maintainer makes if/when they
52 merge the pull request. So write it up well, as it will be in the kernel
59 want to use that message as the message for the merge, so it should
67 suspicious. And when you send me new stuff after the merge window
70 happened that this didn't go through the merge window..
83 it right now), but may not make sense in the context of a merge
95 Here is the big char/misc patch set for the 4.15-rc1 merge window.
/Linux-v6.6/drivers/gpu/drm/ci/
Dgitlab-ci.yml118 # Forked project branch / pre-merge pipeline not for Marge bot
119 …- if: &is-forked-branch-or-pre-merge-not-for-marge '$CI_PROJECT_NAMESPACE != "mesa" || ($GITLAB_US…
124 # Post-merge pipeline
125 - if: &is-post-merge '$CI_PROJECT_NAMESPACE == "mesa" && $CI_COMMIT_BRANCH'
127 # Post-merge pipeline, not for Marge Bot
128 …- if: &is-post-merge-not-for-marge '$CI_PROJECT_NAMESPACE == "mesa" && $GITLAB_USER_LOGIN != "marg…
130 # Pre-merge pipeline
131 - if: &is-pre-merge '$CI_PIPELINE_SOURCE == "merge_request_event"'
133 # Pre-merge pipeline for Marge Bot
134 …- if: &is-pre-merge-for-marge '$GITLAB_USER_LOGIN == "marge-bot" && $CI_PIPELINE_SOURCE == "merge_…
[all …]
/Linux-v6.6/Documentation/admin-guide/device-mapper/
Dsnapshot.rst12 - 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-v6.6/drivers/gpu/drm/mediatek/
Dmtk_disp_merge.c163 * DISP_REG_MERGE_CFG_24 is merge SRAM0 w/h in mtk_merge_advance_config()
164 * DISP_REG_MERGE_CFG_25 is merge SRAM1 w/h. in mtk_merge_advance_config()
165 * If r_w > 0, the merge is in merge mode (input0 and input1 merge together), in mtk_merge_advance_config()
167 * If r_w = 0, the merge is in buffer mode, the input goes through SRAM0 and in mtk_merge_advance_config()
180 * DISP_REG_MERGE_CFG_26 and DISP_REG_MERGE_CFG_27 is only used in LR merge. in mtk_merge_advance_config()
181 * Only take effect when the merge is setting to merge mode. in mtk_merge_advance_config()
201 dev_err(dev, "merge clk prepare enable failed\n"); in mtk_merge_clk_enable()
255 dev_err(dev, "failed to ioremap merge\n"); in mtk_disp_merge_probe()
261 dev_err(dev, "failed to get merge clk\n"); in mtk_disp_merge_probe()
267 dev_err(dev, "failed to get merge async clock\n"); in mtk_disp_merge_probe()
[all …]
/Linux-v6.6/lib/
Dlist_sort.c12 * to chaining of merge() calls: null-terminated, no reserved or
16 static struct list_head *merge(void *priv, list_cmp_func_t cmp, in merge() function
45 * Combine final list merge with restoration of standard doubly-linked
46 * list structure. This approach duplicates code from merge(), but
83 * If the merge is highly unbalanced (e.g. the input is in merge_final()
144 * for each bit, when count increments to 2^k), we merge two lists of
147 * This merge happens exactly when the count reaches an odd multiple of
149 * so it's safe to merge away two lists of size 2^k.
170 * (merge and loop back to state 2)
174 * merge them away in the 5->2 transition. Note in particular that just
[all …]
/Linux-v6.6/tools/lib/
Dlist_sort.c11 * to chaining of merge() calls: null-terminated, no reserved or
15 static struct list_head *merge(void *priv, list_cmp_func_t cmp, in merge() function
44 * Combine final list merge with restoration of standard doubly-linked
45 * list structure. This approach duplicates code from merge(), but
82 * If the merge is highly unbalanced (e.g. the input is in merge_final()
143 * for each bit, when count increments to 2^k), we merge two lists of
146 * This merge happens exactly when the count reaches an odd multiple of
148 * so it's safe to merge away two lists of size 2^k.
169 * (merge and loop back to state 2)
173 * merge them away in the 5->2 transition. Note in particular that just
[all …]
/Linux-v6.6/fs/btrfs/
Dextent_map.c185 /* Check to see if two extent_map structs are adjacent and safe to merge. */
192 * don't merge compressed extents, we need to know their in mergable_maps()
203 * We don't want to merge stuff that hasn't been written to the log yet in mergable_maps()
233 struct extent_map *merge = NULL; in try_merge_map() local
250 merge = rb_entry(rb, struct extent_map, rb_node); in try_merge_map()
251 if (rb && mergable_maps(merge, em)) { in try_merge_map()
252 em->start = merge->start; in try_merge_map()
253 em->orig_start = merge->orig_start; in try_merge_map()
254 em->len += merge->len; in try_merge_map()
255 em->block_len += merge->block_len; in try_merge_map()
[all …]
/Linux-v6.6/drivers/net/ethernet/netronome/nfp/flower/
Doffload.c586 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 …]
Dconntrack.h127 * @flags: Used to indicate flow flag like NAT which used by merge.
148 * struct nfp_fl_ct_tc_merge - Merge of two flows from tc
170 * struct nfp_fl_nft_tc_merge - Merge of tc_merge flows with nft flow
221 * merge with other +trk+est entries and offload if possible.
238 * merge with other -trk entries and offload if possible.
252 * to the next relevant zone table. Try to merge with other +trk+est
/Linux-v6.6/block/
Dblk-merge.c3 * Functions related to segment and merge handling
61 * Don't merge if the 1st bio starts with non-zero offset, otherwise it in bio_will_gap()
63 * merge a huge number of small single bios in case of mkfs. in bio_will_gap()
79 * merge with 'pb' in bio_will_gap()
378 /* there isn't chance to merge the split bio */ in __bio_split_to_limits()
505 /* only try to merge bvecs into one sg if they are from two bios */
539 * Only try to merge bvecs from two bios given we in __blk_bios_map_sg()
540 * have done bio internal merge when adding pages in __blk_bios_map_sg()
617 /* discard request merge won't add new segment */ in ll_new_hw_segment()
719 /* Merge is OK... */ in ll_merge_requests_fn()
[all …]
/Linux-v6.6/tools/perf/tests/
Dmaps.c126 TEST_ASSERT_VAL("failed to merge map", !ret); in test__maps__merge_in()
129 TEST_ASSERT_VAL("merge check failed", !ret); in test__maps__merge_in()
132 TEST_ASSERT_VAL("failed to merge map", !ret); in test__maps__merge_in()
135 TEST_ASSERT_VAL("merge check failed", !ret); in test__maps__merge_in()
138 TEST_ASSERT_VAL("failed to merge map", !ret); in test__maps__merge_in()
141 TEST_ASSERT_VAL("merge check failed", !ret); in test__maps__merge_in()
/Linux-v6.6/Documentation/process/
D2.Process.rst37 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 …]
D7.AdvancedTopics.rst65 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-v6.6/tools/testing/selftests/arm64/mte/
Dcheck_ksm_options.c122 /* Tagged pages should not merge */ in check_madvise_options()
154 "Check KSM mte page merge for private mapping, sync mode and mmap memory\n"); in main()
156 "Check KSM mte page merge for private mapping, async mode and mmap memory\n"); in main()
158 "Check KSM mte page merge for shared mapping, sync mode and mmap memory\n"); in main()
160 "Check KSM mte page merge for shared mapping, async mode and mmap memory\n"); in main()
/Linux-v6.6/arch/nios2/lib/
Dmemcpy.c31 #define MERGE(w0, sh_1, w1, sh_2) (((w0) >> (sh_1)) | ((w1) << (sh_2))) macro
137 ((op_t *) dstp)[0] = MERGE(ap, sh_1, a0, sh_2); in _wordcopy_fwd_dest_aligned()
138 ((op_t *) dstp)[1] = MERGE(a0, sh_1, a1, sh_2); in _wordcopy_fwd_dest_aligned()
139 ((op_t *) dstp)[2] = MERGE(a1, sh_1, a2, sh_2); in _wordcopy_fwd_dest_aligned()
140 ((op_t *) dstp)[3] = MERGE(a2, sh_1, a3, sh_2); in _wordcopy_fwd_dest_aligned()
151 ((op_t *) dstp)[0] = MERGE(ap, sh_1, a0, sh_2); in _wordcopy_fwd_dest_aligned()
/Linux-v6.6/Documentation/devicetree/bindings/riscv/
Dextensions.yaml128 changes to interrupts as frozen at commit ccbddab ("Merge pull
136 ("Merge pull request #42 from riscv/jhauser-2023-RC4") of riscv-aia.
171 acceleration instructions as ratified at commit 6d33919 ("Merge pull
178 as ratified at commit 6d33919 ("Merge pull request #158 from
184 multiplication as ratified at commit 6d33919 ("Merge pull request
190 instructions as ratified at commit 6d33919 ("Merge pull request #158
/Linux-v6.6/fs/notify/
Dnotification.c73 * The group can use the @merge hook to merge the event with a queued event.
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-v6.6/Documentation/block/
Ddeadline-iosched.rst62 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-v6.6/tools/testing/selftests/sync/
Dsync_stress_merge.c12 * the rights to use, copy, modify, merge, publish, distribute, sublicense,
60 * and merge them together in test_merge_stress_random_merge()
74 /* Merge */ in test_merge_stress_random_merge()
76 merged = sync_merge("merge", tmpfence, fence); in test_merge_stress_random_merge()
/Linux-v6.6/Documentation/driver-api/media/
Dv4l2-event.rst59 ``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-v6.6/arch/sparc/include/asm/
Destate.h17 * fetches 3) atomic operations. Such events _cannot_ occur for: 1) merge
29 * 3) As the result of store merge completion, writeback, or copyout will
43 * during store merge, writeback, and copyout operations.
/Linux-v6.6/net/batman-adv/
Dfragmentation.c134 * fragments needed to merge the packet, the chain is moved to the passed head
150 * the later merge. Non-linear merge should be added to remove this in batadv_frag_insert_packet()
239 * batadv_frag_merge_packets() - merge a chain of fragments
298 * batadv_frag_skb_buffer() - buffer fragment for later merge
302 * Add fragment to buffer and merge fragments if possible.
318 /* Add packet to buffer and table entry if merge is possible. */ in batadv_frag_skb_buffer()
322 /* Leave if more fragments are needed to merge. */ in batadv_frag_skb_buffer()
453 /* To avoid merge and refragmentation at next-hops we never send in batadv_frag_send_packet()

12345678910>>...130