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 14F76C4338F for ; Sun, 22 Aug 2021 00:24:25 +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 5D47C61206 for ; Sun, 22 Aug 2021 00:24:24 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 5D47C61206 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=vt.edu 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 1mHbHQ-0000H5-9f; Sat, 21 Aug 2021 20:24:04 -0400 Received: from mail-qv1-xf35.google.com ([2607:f8b0:4864:20::f35]) by shelob.surriel.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1mHbHK-0000GO-0Z for kernelnewbies@kernelnewbies.org; Sat, 21 Aug 2021 20:23:58 -0400 Received: by mail-qv1-xf35.google.com with SMTP id j9so7695634qvt.4 for ; Sat, 21 Aug 2021 17:23:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vt-edu.20150623.gappssmtp.com; s=20150623; h=sender:from:to:cc:subject:in-reply-to:references:mime-version :content-transfer-encoding:date:message-id; bh=2EnpN7+ZCrylqw0iyfC5t6Ax77Z2G2CwrLYam9FQdho=; b=vP1CnxddCdPuVkvM2LpF/Vwc1XlVa0ui7FqFqVSVnk9yy1EydbQeP9Pls+iFfdaes8 N7B1HCGpo/yal0pSe3Hupi6t2kuMqEcGD0AgcU6dOzamXibsvrh25heXMo7a6/SX39Mb JzTGql7Crek1pUPIHIFo4SwJj/o0TKHSY1BdBos4hfgJ898C8QLBuDEp5bvDiifvVFud AxOt1MX0+R8zuG9IUo+ne2DNhXvZxgEEW63ibV+mL8CWx+fB4tC2YPVLz1egu8zSRpDY 6Dc/QoPdNX9vth5u9EA++fGgSUZePBCa2t+9DI19pTHlL6os34EUaPkvs+EW078BClD6 kVZQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:to:cc:subject:in-reply-to:references :mime-version:content-transfer-encoding:date:message-id; bh=2EnpN7+ZCrylqw0iyfC5t6Ax77Z2G2CwrLYam9FQdho=; b=WqhSwsEbZWTnybpmBPUFeHtPVVU7umHdju3KZqbjp1+vfEjGgisj2kuziblQEfrchi fbbIBTru8CY7Hiaufq2qTHL9LGEs+0do1q7mCNQ6zxZ9ZaKO4Yjw286L7xjeZkV3ZEmk CUBqHnRZeDbuQR3Qm4asIKTyF2E/s54Y3QQK9YCa7XT4HcS1cuAZ8upQ2NQOnQdcvuuG 5PaEuB5pT1/tzBfhQWcuK8cuU/AJItliI/Wh63cfqx++f/+bVhlSuChfseoa/RACRcjC s0hMhgP8AmS/09733olJmJkT/tD0DZWLJ6Fx4R41IXDx+P1gwTFJfQqOfK97wjYqPLKS WAdw== X-Gm-Message-State: AOAM533It5PY3qN4xRKgrGhyhlOMHR9WxusZIzQ4IiVPBiAs2LTBFOyE kKSCUG69tBM/l0ZGfIK75KmlBA== X-Google-Smtp-Source: ABdhPJzh7AanrMoIsaj0dIGKh1J29UTjBCaEsnv42qu59i3JSnnV00Vm0Vx7VtNYdhwGAYWZcmyLow== X-Received: by 2002:a05:6214:10c4:: with SMTP id r4mr27098318qvs.58.1629591835263; Sat, 21 Aug 2021 17:23:55 -0700 (PDT) Received: from turing-police ([2601:5c0:c380:d61::359]) by smtp.gmail.com with ESMTPSA id g11sm4253901qtk.50.2021.08.21.17.23.54 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 21 Aug 2021 17:23:54 -0700 (PDT) From: "Valdis Kl=?utf-8?Q?=c4=93?=tnieks" X-Google-Original-From: "Valdis Kl=?utf-8?Q?=c4=93?=tnieks" X-Mailer: exmh version 2.10.0-pre 07/05/2021 with nmh-1.7+dev To: daniel watson Subject: Re: how do you find the subsystem of a file? In-Reply-To: <20210821231931.GB7414@challenge-bot.com> References: <20210821073027.GD18204@challenge-bot.com> <20210821231931.GB7414@challenge-bot.com> Mime-Version: 1.0 Date: Sat, 21 Aug 2021 20:23:53 -0400 Message-ID: <270834.1629591833@turing-police> 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: multipart/mixed; boundary="===============6426676205011050389==" Errors-To: kernelnewbies-bounces@kernelnewbies.org --===============6426676205011050389== Content-Type: multipart/signed; boundary="==_Exmh_1629591833_136257P"; micalg=pgp-sha256; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit --==_Exmh_1629591833_136257P Content-Type: text/plain; charset=us-ascii On Sat, 21 Aug 2021 16:19:31 -0700, daniel watson said: > On Sat, Aug 21, 2021 at 12:30:27AM -0700, daniel watson wrote: > > Documentation/process/submitting-patches.rst says to see the T: entry > > for the subsystem in MAINTAINERS to find the right tree to base the > > patch on. If there's no better entry listed in a T:, the linux-next tree is a good default. Failing that, a recent pull of Linus's tree is usually OK (though can cause issues with conflicts if other people are working on the area and their patches are in linux-next already). Since the linux-next tree is rebuild every day, it's usually only 24 hours or so behind the 200+ maintainer trees that feed it. The quick cheat sheet for linux-next: $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git $ git remote add linux-next git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git $ git fetch linux-next $ git fetch --tags linux-next ... # later on $ git remote update $ git checkout next-20210820 (or whatever the one you want is) Don't use 'git pull' against a linux-next tree, as it won't do what you want, use 'remote update'. (The gory details - it rebases every day due to the way it is built) Also, you can bisect between a 'next-20210605' tag and a Linus 'v5.13-rc3' type tag, but bisecting between two 'next-mmm' tags will fail, for the same reasons that git pull will blow chunks. > > in addition, how do i know what branch to use? the T: entries have a > > repo, but not a branch name. You want it pointing at master/HEAD unless you have a *damned* good reason to use something else (usually "maintainer specifically told you to use a different branch") > the output of > > git log --oneline -1 > > should have the subsystem listed at the beginning. Actually, it's not *necessarily* 'subsystem' - it's "what the tree maintainer wants as the start of the Subject: line", which can sometimes be different. --==_Exmh_1629591833_136257P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Comment: Exmh version 2.9.0 11/07/2018 iQEcBAEBCAAGBQJhIZkZAAoJEI0DS38y7CIcP3QH/2FzLIhUVO0dDlmvlA+B7Ycw 1Q0Gorg26ZoJ3EWjEMhra3OBTSivArYk2QnZkOgHpyTo554aQI2GaxNrr4gNXuh3 OCUlQ0QB88DfBjCBQGV19UbOlFf8MJ35lD/BnRlf6ZpypWFWGC+QXTm6bMyOsQde MESU3O9h6qMYA2Hp/jAxD31aci8s8OU0oAy5BXWCvNuB3r8AEI2jiPbx6HlY6qAN EehNlcBPuB9SkXoFBwW9kRACQ5m0h5rOFWlLJClyJfNy/ZEYss+W72ikeE+0hWu5 58TsUDSAHi2ZPkv+1MH3iQgCRY9pgmQpCIJKRuP06rRefXD1MgFkZViYK+AX+OY= =vrcF -----END PGP SIGNATURE----- --==_Exmh_1629591833_136257P-- --===============6426676205011050389== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies --===============6426676205011050389==--