From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Wojciech Kudla <wk.kernel@gmail.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: First patch questions (target mailing list, target tree)
Date: Sun, 10 May 2020 18:55:16 -0400 [thread overview]
Message-ID: <81190.1589151316@turing-police> (raw)
In-Reply-To: <r99dg3$35gt$1@ciao.gmane.io>
[-- Attachment #1.1: Type: text/plain, Size: 1084 bytes --]
On Sun, 10 May 2020 18:26:27 +0100, Wojciech Kudla said:
> I'd like to send a patch to arch/x86/kernel/smp.c but I'm not sure about
> 1) which branch of whose tree do I crate the patch against?
> According to MAINTAINERS:
T: git git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
There you go. In general, you're usually OK using either the current Linus
tree or linux-next tree. Unless you're doing work that directly intersects
with other development, those should be quite good enough.
Linus's tree:
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
To add linux-next to that:
$ 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
Don't use 'git pull' against linux-next, because it's rebuilt every day.
Strange and wondrous things will happen. That also means that you
can't git bisect between (say) next-20200405 and next-20200503 (though
you can bisect between a Linus v5.7-rc3 tag and a next- tag )
[-- Attachment #1.2: Type: application/pgp-signature, Size: 832 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:[~2020-05-10 22:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-10 17:26 First patch questions (target mailing list, target tree) Wojciech Kudla
2020-05-10 18:12 ` Konstantin Ryabitsev
2020-05-10 18:55 ` Wojciech Kudla
2020-05-10 18:55 ` Wojciech Kudla
2020-05-10 22:55 ` Valdis Klētnieks [this message]
2020-05-11 5:21 ` Wojciech Kudla
2020-05-11 5:21 ` Wojciech Kudla
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=81190.1589151316@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=kernelnewbies@kernelnewbies.org \
--cc=wk.kernel@gmail.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).