From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: daniel watson <ozzloy@challenge-bot.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: how do you find the subsystem of a file?
Date: Sat, 21 Aug 2021 20:23:53 -0400 [thread overview]
Message-ID: <270834.1629591833@turing-police> (raw)
In-Reply-To: <20210821231931.GB7414@challenge-bot.com>
[-- Attachment #1.1: Type: text/plain, Size: 1942 bytes --]
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 <path>
>
> 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.
[-- Attachment #1.2: Type: application/pgp-signature, Size: 494 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2021-08-22 0:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-21 7:30 how do you find the subsystem of a file? daniel watson
2021-08-21 23:19 ` daniel watson
2021-08-22 0:23 ` Valdis Klētnieks [this message]
2021-09-01 6:37 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=270834.1629591833@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=kernelnewbies@kernelnewbies.org \
--cc=ozzloy@challenge-bot.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).