From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.6 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0296CC433F5 for ; Sat, 11 Sep 2021 08:18:45 +0000 (UTC) Received: from shelob.surriel.com (shelob.surriel.com [96.67.55.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 871C46108B for ; Sat, 11 Sep 2021 08:18:44 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 871C46108B Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=kroah.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=kernelnewbies.org Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.94.2) (envelope-from ) id 1mOyCK-0002Nm-SI; Sat, 11 Sep 2021 04:17:16 -0400 Received: from wout4-smtp.messagingengine.com ([64.147.123.20]) by shelob.surriel.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1mOyCH-0002ND-7d for kernelnewbies@kernelnewbies.org; Sat, 11 Sep 2021 04:17:13 -0400 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id C5D01320094E; Sat, 11 Sep 2021 04:17:08 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Sat, 11 Sep 2021 04:17:09 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kroah.com; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm1; bh=ZCHbiAcPUwVdZgSlkFrmptaFkeC J+1de6MZLHEz8D50=; b=qVNNE2yNuTpCt6rnCdk/5+wKOlymZqDbeSyCI2fUYsU 0OEUypBw2qtDWrSltrBiix7v1zJq3kSdxemJfj2QpHvOyjlHwhK0cMAcynpGHyWX 6ywxcQXFrt7ZeoSxUfQbvYMVVHjfFPqi2afwsjFY6LdGBK6UcGNl7nRas1eU1QJy GacWPRIhEX8n9BPatuKlKmlGtOPmxYavfwC6n1hYUqUzgSbFbI3pE6tqfYs95B9O DdIhJdIK0qVBoIU0DxEZw/y2mRu8pVHAuUEz62Fe/9yqy2NnTM6K3zJV+WEPLw1M zyEHdQoLgP73AysWFqXZtRWZdmIJfBj98PQWTqnLDhw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=ZCHbiA cPUwVdZgSlkFrmptaFkeCJ+1de6MZLHEz8D50=; b=XKs2gaE11u8+29Zi+jREL/ vns4lNCaUfU0wtioUdo73cA9okjhGUqjnHCIF+dDuzV/yAKJXlJBjR4FsJPbggFn 7OvLKwCwVmLv5PDrER3h9MDNVNYRTBWzCgajtvMJvPxmgZFdOCg6jY5hdXDjzJY7 pjpBw3vtoylcp7gTNWga6U5Fu8k6BvTQEryIeu64SEP6OWAnyXS0CkqSgs+3p3Ve oIdmcXRa9IU+jRxaUGUpUVD3yyCgZ0mWXDBlmcxyk9TebEOhSIxiGX+S8kANNfyp fm7dWp/4epHzB3q8BH2hOeK2yQcPMu1/PN6B6cMhdOkHKiVMLj3B+JktmyNAC/mg == X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrudegfedgtddvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkfhggtggujgesthdtre dttddtvdenucfhrhhomhepifhrvghgucfmjfcuoehgrhgvgheskhhrohgrhhdrtghomheq necuggftrfgrthhtvghrnhepueelledtheekleethfeludduvdfhffeuvdffudevgeehke egieffveehgeeftefgnecuffhomhgrihhnpehkvghrnhgvlhdrohhrghenucevlhhushht vghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehgrhgvgheskhhrohgrhh drtghomh X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sat, 11 Sep 2021 04:17:07 -0400 (EDT) Date: Sat, 11 Sep 2021 10:16:45 +0200 From: Greg KH To: Lafan Mining Subject: Re: Understanding merge window and next-tree Message-ID: References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: Cc: "kernelnewbies@kernelnewbies.org" X-BeenThere: kernelnewbies@kernelnewbies.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Learn about the Linux kernel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: kernelnewbies-bounces@kernelnewbies.org On Fri, Sep 10, 2021 at 04:06:39PM +0000, Lafan Mining wrote: > I'm trying to understand how Linux Kernel development works and reading the relevant documentation at https://www.kernel.org/doc/html/latest/process/2.Process.html > > So there is the so called next-tree accumulating all the patches from all the subsystems ready for merge and the mainline tree. The thing is the merge-window is opened for 2 weeks (as mentioned in the linked documentation) and as far as I understood all the changes will be merged into the mainline. > > But looking through the next-tree I found some implementation in Rust https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/log/rust which is much older than 2 months. > > How is that happened that after a few merge windows (4 if I counted correctly) it's still not merged? Maintainers have to ask Linus to take their changes and be merged, Linus does not directly merge from linux-next. This allows for maintainers to "skip" merge windows if needed, as well as have things in linux-next for a long time before they go to Linus for various reasons (the -mm tree has many such patches, and so does the rust tree as you have seen.) So yes, the requirement is that changes have to be in linux-next before it goes into Linus's tree, but it does not guarantee that anything is in linux-next will end up in Linus's tree. Does that help? greg k-h _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies