Skip to contentSkip to conversation

What version should I be patching against?

DISCUSSION Dolan Murvihill 5 participants 6 messages Jul 30, 2013 Kernel janitors

lore
Share & tools
lore
#0 lore raw

Q: What version should I be patching against?

I saw this answer in the FAQ on https://code.google.com/p/kernel-janitors/ :

A: Latest "linus" (2.6.x-rcY from kernel.org).

Two questions about this:
1. Is this still current? My understanding was that we moved past 2.6 long ago, and any changes would be ported from the latest 3.x release.

2. Did you mean "torvalds", or is there another tree called "linus"?

For now, I'm going to work with Linus' tree at
pub/scm/linux/kernel/git/torvalds/linux.git.

-Dolan

#1 lore raw

Wow... Yes. That information is totally out of date. Do patches against the daily linux-next. Don't do them against mainline.

regards,
dan carpenter

#2 lore raw
In reply to Dolan Murvihill
Quoted 2 lines · Dan Carpenter

Wow... Yes. That information is totally out of date. Do patches against the daily linux-next. Don't do them against mainline.

these commands would be useful to add

$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
$ cd linux
$ 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
...
Signature · 1 line
Nikola
#3 lore raw
In reply to Dolan Murvihill

That's really good information, thank you.

Dan, I recently submitted a patch and the message back was:

"This is a note to let you know that I've just added the patch titled

staging: comedi: dt9812: Resolves sparse endian warnings.

to my staging git tree which can be found at
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git
in the staging-next branch.
"

Is it wrong to be patching against this
(git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git),
then? (I also see a reference to this at
https://code.google.com/p/kernel-janitors/wiki/TODO under "Linux-Staging Tree").

#4 lore raw
In reply to Dolan Murvihill
Quoted 9 lines

Dan, I recently submitted a patch and the message back was:

"This is a note to let you know that I've just added the patch titled

staging: comedi: dt9812: Resolves sparse endian warnings.

to my staging git tree which can be found at
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git
in the staging-next branch.

Congratulations,

This is a message from Greg Kroah-Hartman workflow, your patch will be part of the next kernel release (3.12).

Signature · 3 lines
« On ne résout pas un problème avec les modes de pensée qui l’ont engendré. »
« You cannot solve current problems with current thinking. Current
problems are the result of current thinking »
#5 lore raw
In reply to Dolan Murvihill
Quoted 13 lines · Shaun Laing

That's really good information, thank you.

Dan, I recently submitted a patch and the message back was:

"This is a note to let you know that I've just added the patch titled

staging: comedi: dt9812: Resolves sparse endian warnings.

to my staging git tree which can be found at
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git
in the staging-next branch.
"

Quoted 5 lines

Is it wrong to be patching against this
(git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git),
then? (I also see a reference to this at
https://code.google.com/p/kernel-janitors/wiki/TODO under "Linux-Staging Tree").

Stephen Rothwell creates linux-next daily. He takes everyone's development trees and merges them.

regards,
dan carpenter