ftg has quit [Read error: Connection reset by peer]
apritzel has quit [Ping timeout: 480 seconds]
Daanct12 has joined #linux-sunxi
vagrantc has quit [Quit: leaving]
chewitt has joined #linux-sunxi
hexdump01 has joined #linux-sunxi
hexdump0815 has quit [Ping timeout: 480 seconds]
hexdump0815 has joined #linux-sunxi
hexdump01 has quit [Ping timeout: 480 seconds]
apritzel has joined #linux-sunxi
JohnDoe_71Rus has joined #linux-sunxi
apritzel has quit [Ping timeout: 480 seconds]
gamiee has quit [Read error: Connection reset by peer]
ctag has quit [Ping timeout: 480 seconds]
warpme has joined #linux-sunxi
gsz has joined #linux-sunxi
fuyao has joined #linux-sunxi
fuyao has quit [Remote host closed the connection]
fuyao has joined #linux-sunxi
gsz has quit [Quit: leaving]
apritzel has joined #linux-sunxi
warpme has quit [Read error: Connection reset by peer]
warpme has joined #linux-sunxi
warpme has quit []
fuyao has quit []
warpme has joined #linux-sunxi
Net147 has quit [Quit: Quit]
Net147 has joined #linux-sunxi
warpme has quit [Read error: Connection reset by peer]
dsimic is now known as Guest11292
dsimic has joined #linux-sunxi
Guest11292 has quit [Ping timeout: 480 seconds]
<apritzel>
jernej: wens: smaeul: any idea where the base-commit: tag in a patch email is allowed to come from? Does that need to be from Linus' tree? Is -next fine? Or any other repo hosted on kernel.org?
<apritzel>
I wanted to send something on top of sunxi/for-next (or sunxi/dt-for-6.8, really)
chewitt has quit [Quit: Zzz..]
wasutton3 has joined #linux-sunxi
wasutton- has quit [Ping timeout: 480 seconds]
Daanct12 has quit [Quit: WeeChat 4.1.2]
warpme has joined #linux-sunxi
JohnDoe_71Rus has quit []
warpme has quit []
ctag has joined #linux-sunxi
<apritzel>
nvm, I based it on latest master, and just pulled in the two patches from dt-for-6.8 that conflict, which get their patch-id automatically mentioned as a prerequisite
JohnDoe_71Rus has joined #linux-sunxi
warpme has joined #linux-sunxi
ctag has quit []
evgeny_boger has quit [Quit: evgeny_boger]
cp- has joined #linux-sunxi
cp-- has quit [Ping timeout: 480 seconds]
kuba2k2 has joined #linux-sunxi
<jernej>
apritzel: it's usually better if you just state what is your base in cover letter or below ---
<jernej>
sunxi/for-next is unstable and so is linux-mext
<jernej>
but sunxi/dt-for-6.8 should keep commit hashes intact
<apritzel>
jernej: thanks, and also figured something human parse-able would be best, so I added one line after the three dashes to spell this out
warpme has quit []
warpme has joined #linux-sunxi
norton has joined #linux-sunxi
warpme has quit []
macromorgan_ has joined #linux-sunxi
macromorgan has quit [Ping timeout: 480 seconds]
warpme has joined #linux-sunxi
apritzel has quit [Quit: Leaving]
diego71 has quit [Ping timeout: 480 seconds]
warpme has quit []
diego71 has joined #linux-sunxi
warpme has joined #linux-sunxi
warpme has quit [Read error: Connection reset by peer]