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.3 required=3.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, 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 93C59C4363D for ; Wed, 23 Sep 2020 02:09:10 +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 F065A2371F for ; Wed, 23 Sep 2020 02:09:09 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="CXLH4I2x" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org F065A2371F Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.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 1kKuDB-0003xc-8Z; Tue, 22 Sep 2020 22:08:49 -0400 Received: from mail-pf1-x441.google.com ([2607:f8b0:4864:20::441]) by shelob.surriel.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94) (envelope-from ) id 1kKuD8-0003xX-GE for kernelnewbies@kernelnewbies.org; Tue, 22 Sep 2020 22:08:46 -0400 Received: by mail-pf1-x441.google.com with SMTP id k13so13580926pfg.1 for ; Tue, 22 Sep 2020 19:08:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:mime-version:content-disposition; bh=gr7rXxZX6sAmaoMHeePPYdxQOA4PH+tttHtlHpXyW58=; b=CXLH4I2xiQAaFcYhDdbzl5cIzvDsSWRMVf5Zkpl3ADatdXwCEx6I7Gjyx2rdq1QvwC ydzc8RS0AxLHl0xgvIzytP7pwFVG6GB98f68r+qL6pYPO2atXGhoXW/sJPkubqBNe+9B +r76I2P/uzv3JgoqX6U1BWYlcSqDS9aT4wje5aJl5sCOB2moaVZ8XSHmSy2drrl13wSO BxmCVpagj5NZcrk+yPqhTGXoHBc1ousF2QXmaxj2+Q9AeP7rx7fu6FLbGx5S3HF43/nm EB+e47y0TqthndBxH6TNZTtQQrl7W/QY38EaXv7q1q49jac3fcr26QJsY/4/Rk604fTC Q8cQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:mime-version :content-disposition; bh=gr7rXxZX6sAmaoMHeePPYdxQOA4PH+tttHtlHpXyW58=; b=M20tyJROYQR3cxcng7q4LotNQkozaYzYv3LhMrPeuqYZn2aaksqDwzf8sNcinzN16M lrd208rer7ly3NocFHfVgSF0cFh0L0YFFsTFbZnFtx3YfUwBoOOIuju4O7iHR5ymfWw+ Kgu84RdDmAeqPSX7RZ6cv/LzM39iJFdb4wLUygvVh0qtYJ7554mM/qmorgdr0Lv4gEYk ovwbhk+OMLvozg3eFGIvLhXH4e5+3uEfuxAOidPMn2j7CsCZGzaTyoLfPjbi7xZJcI5t NYC2iAdea++VWBzRC4zIReMXMC8xMUdF+bVQuxp7S4eNrW2H7rqcTjQY/CxUkHdNLefn EK4g== X-Gm-Message-State: AOAM530yMqA6wju5jYCrlSj9E5Fgzvt986kGx2e9tobMTwlnU5LDh8R5 IN13gv+qzLOyKW2mF2EllONious0w3AVIhc8 X-Google-Smtp-Source: ABdhPJy0wfJ2RFrNm5MKFmQcEBSC4ltpwoosJ/9ODbBwbH55OjxqlbieDXYMe5F4aczYw1OKvAp1gQ== X-Received: by 2002:a62:6490:0:b029:13f:c196:bb77 with SMTP id y138-20020a6264900000b029013fc196bb77mr6579602pfb.14.1600826924378; Tue, 22 Sep 2020 19:08:44 -0700 (PDT) Received: from james-Aspire-E5-575G (c-71-231-36-179.hsd1.wa.comcast.net. [71.231.36.179]) by smtp.gmail.com with ESMTPSA id q10sm3323724pja.48.2020.09.22.19.08.43 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 22 Sep 2020 19:08:43 -0700 (PDT) Date: Tue, 22 Sep 2020 19:08:38 -0700 From: James Browning To: kernelnewbies@kernelnewbies.org Subject: Confused about which branch to patch against Message-ID: <20200923020838.uhvm2npdxycieja6@james-Aspire-E5-575G> MIME-Version: 1.0 Content-Disposition: inline Cc: jamesbrowning137@gmail.com 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 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. 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). 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? Thank you for your help, James Browning _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies