Kernel Newbies archive on lore.kernel.org
 help / color / Atom feed
WARNING: multiple messages have this Message-ID
From: Wojciech Kudla <wk.kernel@gmail.com>
To: kernelnewbies@kernelnewbies.org
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: First patch questions (target mailing list, target tree)
Date: Mon, 11 May 2020 06:21:32 +0100
Message-ID: <12f99361-99d3-7675-9f12-a03a27f6cf7e@gmail.com> (raw)
In-Reply-To: <81190.1589151316@turing-police>

On 10/05/2020 23:55, Valdis Klētnieks wrote:
> 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 )
> 
> 
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
> 

This is exactly what I was looking for. Thank you!


_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

From: Wojciech Kudla <wk.kernel@gmail.com>
To: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: First patch questions (target mailing list, target tree)
Date: Mon, 11 May 2020 06:21:32 +0100
Message-ID: <12f99361-99d3-7675-9f12-a03a27f6cf7e@gmail.com> (raw)
Message-ID: <20200511052132.ELDLER_mSrt_FykFvAFGIFPHNCzRSqtTrniDgkwWiHg@z> (raw)
In-Reply-To: <81190.1589151316@turing-police>

On 10/05/2020 23:55, Valdis Klētnieks wrote:
> 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 )
> 
> 
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
> 

This is exactly what I was looking for. Thank you!

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  reply index

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-10 17:26 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
2020-05-11  5:21   ` Wojciech Kudla [this message]
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=12f99361-99d3-7675-9f12-a03a27f6cf7e@gmail.com \
    --to=wk.kernel@gmail.com \
    --cc=kernelnewbies@kernelnewbies.org \
    /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

Kernel Newbies archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/kernelnewbies/0 kernelnewbies/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 kernelnewbies kernelnewbies/ https://lore.kernel.org/kernelnewbies \
		kernelnewbies@kernelnewbies.org
	public-inbox-index kernelnewbies

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernelnewbies.kernelnewbies


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git