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.8 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,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 DBB4AC4346E for ; Sun, 27 Sep 2020 06:28:13 +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 50E6823A01 for ; Sun, 27 Sep 2020 06:28:13 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=kernel.org header.i=@kernel.org header.b="apLj5WjT" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 50E6823A01 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org 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 1kMQA2-0003oH-22; Sun, 27 Sep 2020 02:27:50 -0400 Received: from mail.kernel.org ([198.145.29.99]) by shelob.surriel.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94) (envelope-from ) id 1kMQ9z-0003oC-Vh for kernelnewbies@kernelnewbies.org; Sun, 27 Sep 2020 02:27:48 -0400 Received: from localhost (unknown [213.57.247.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id C4E6D23A04; Sun, 27 Sep 2020 06:27:45 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1601188066; bh=5J7dFi3HRT0H6ObqS9t6boKXixrQo1YcFYDhGh1oiDc=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=apLj5WjTzYiCCcEles0/AwZ/mGgQ6Si73VVvmX2LmUKMI1t6LSi6vJUJeP2iGOo1O hAsTtPCrALCVMU2BAf2awjhIvNkCoQyG40BK4ZPyKORyClZpU4QXn0sxuoBOLgx9j+ ItNTt/fowkV7gLwzrUjvSSi3lHI3uhxv28rh+iwc= Date: Sun, 27 Sep 2020 09:27:25 +0300 From: Leon Romanovsky To: "Gustavo A. R. Silva" Subject: Re: Confused about which branch to patch against Message-ID: <20200927062725.GF2280698@unreal> References: <20200923020838.uhvm2npdxycieja6@james-Aspire-E5-575G> <499de2f7-a2b5-5323-38ff-a486fbc40a38@embeddedor.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <499de2f7-a2b5-5323-38ff-a486fbc40a38@embeddedor.com> Cc: James Browning , 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 Tue, Sep 22, 2020 at 09:39:41PM -0500, Gustavo A. R. Silva wrote: > Hi, > > On 9/22/20 21:08, James Browning wrote: > > Hi all, > > > > After reading through the kernel documentation about submitting pathces, > > and reading through the kernel newbies guide to submitting patches, I > > still have some confusion. > > > > Should I be doing all of my patching against linux-next as opposed to > > the mainline tree? I tried submitting a patch to some typos I found on > > the mainline tree, but they were rejected because they had already been > > fixed in linux-next. > > Yes; bleeding edge development happens in linux-next. Just notice that > there is a new linux-next everyday. This is, linux-next is merely a daily > merge of all the individual development '-next' trees. > > Don't get discouraged if your patches are not applied because someone > else already sent a patch to fix the same issue. That certainly happens > every now and then. > > I suggest you to start your journey by addressing issues in staging, first. > Especially, typos and coding style issues. Also, this is a great resource: > > https://kernelnewbies.org/Outreachyfirstpatch > > Read it thoroughly. :) > > > I guess I dont really understand what patches become part of the next > > mainline rc-x tree, and which patches become part of linux-next (which > > from what I understand, doesn't get merged until the next merge window when the current kernel version is finished being stabalized). > > I encourage you to enroll in this course: > > https://training.linuxfoundation.org/training/a-beginners-guide-to-linux-kernel-development-lfd103/ > > It's free and there is a section in the beginning that explains all > about the differences between mainline, -rc, linux-next and stable > trees and how they relate to each other. > > > Also, if I patch something in the linux-next tree, do I need to specify > > which tree it is when I send the patch the maintainers? > > Not necessarily. However, some people explicitly ask you to add 'next' to the > subject line. The networking people, in particular. > > In any case, you'll be safe by adding [next] to the subject line, as follows: > > [PATCH][next] subject IMHO it looks clumsy, why don't [PATCH -next]? > > and the maintainers will know that's for their -next tree. Just make sure you > CC all the file maintainers. > > I hope this helps. > > -- > Gustavo > > _______________________________________________ > Kernelnewbies mailing list > Kernelnewbies@kernelnewbies.org > https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies