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=-3.5 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED autolearn=no 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 A0759C433DB for ; Fri, 26 Feb 2021 07:07:40 +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 AC9D464E46 for ; Fri, 26 Feb 2021 07:07:39 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org AC9D464E46 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-bounces@kernelnewbies.org Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.94) (envelope-from ) id 1lFXDb-0008PO-G4; Fri, 26 Feb 2021 02:07:19 -0500 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by shelob.surriel.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94) (envelope-from ) id 1lFXDa-0008PD-4G for kernelnewbies@kernelnewbies.org; Fri, 26 Feb 2021 02:07:18 -0500 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 83D715C0143; Fri, 26 Feb 2021 02:07:14 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Fri, 26 Feb 2021 02:07:14 -0500 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=fm3; bh=ssP6wQg/nMGLspABe6/EDLHAat6 RbRpQ/gVjfl5l4bQ=; b=pPLeisIQZY5IZCB4YhGr4I2PUNZvEgbVhrRR2kQWvqO EndL5MGQtl3XezdBlShRZpEbMtlx/GRcXs8yYOjQUjwESY96slk+aalSGuxGX/b0 W/CFiNasQybv0X0VUchxcjFLOnaJlxMwXuAaD0wpTLoGENoU0ZZlxh/FZFXKWBI0 64Sepbs173OtyYbbDNLh+7l/06lJfyNbCkhEOVBFHpp48Ow38nqP5+6RYpMMJsBV HELCYkus+PDqtViuxA7egjcPBzKksJcqAP3WibSIbCC5DvZgJ0NTNN7jR420lVOk r4Onxts4pL37vw4PPlH1uUZMXi1k5nsVoHV3W/zMpmw== 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=fm2; bh=ssP6wQ g/nMGLspABe6/EDLHAat6RbRpQ/gVjfl5l4bQ=; b=EXnU0o4ygUC/yv1w1Z3N3i klWQc33KF+5exeIYqNQYqqbgrC7NpYti6aEFu7c6OhcC1VkKiWBam3ZBJVZoXXZl PMMlXuT8c6rzpu7EpPiMTmr5jEQcDyjBX58GfwcFJUYjtH8zVUomrF/4O+Qi3sh6 qLUTyoQuFas5h6jBpTANfJMJiBItfUlLu5C25v9385oB9q4IkUymhJIpsR14bt/8 vBWKypy91JvPksWiX5ZJv0fqbQaqOThBsWPQRiMLdJTf5bNWkV6J3GSnFhckI58+ LxyCGSZ6HoX2JPRYfHFsF49OzCLByzpcAiQ9j+EYrgGiCL61Nj1CNOz4mOXft7fg == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrledtgddutdeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkfhggtggujgesthdtre dttddtvdenucfhrhhomhepifhrvghgucfmjfcuoehgrhgvgheskhhrohgrhhdrtghomheq necuggftrfgrthhtvghrnhepveeuheejgfffgfeivddukedvkedtleelleeghfeljeeiue eggeevueduudekvdetnecukfhppeekfedrkeeirdejgedrieegnecuvehluhhsthgvrhfu ihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepghhrvghgsehkrhhorghhrdgtoh hm X-ME-Proxy: Received: from localhost (83-86-74-64.cable.dynamic.v4.ziggo.nl [83.86.74.64]) by mail.messagingengine.com (Postfix) with ESMTPA id 63BF324005B; Fri, 26 Feb 2021 02:07:13 -0500 (EST) Date: Fri, 26 Feb 2021 08:07:11 +0100 From: Greg KH To: wuzhouhui Subject: Re: Fwd: Re: [GIT PULL] PCI changes for v5.12 Message-ID: References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: Cc: kernelnewbies 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, Feb 26, 2021 at 12:54:16PM +0800, wuzhouhui wrote: > I'm confused about what the Linus said. It seemed that the branch cannot > be rebased after merged into linux-next under normal circumstances, why? You should never rebase a public-facing branch. > Linus found this issue by check commit time of commits, but I also found so > many commit in mainline are too young to be merged into linux-next before > merge to mainline. If the rebase is not recommended, why people like to > do rebase after commits are merged into linux-next? What commits have you found, and are you sure those are not just merged through email submissions to Linus instead of a git tree pull? Please note that some subsystems still use email, like Andrew Morton's. As for why people like to rebase, I do not know, you will have to ask them why they like to do bad things :) does this help? greg k-h _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies