kaspter has quit [Read error: Connection reset by peer]
kaspter has joined #linux-rockchip
camus1 has joined #linux-rockchip
kaspter has quit [Remote host closed the connection]
camus1 is now known as kaspter
vstehle has quit [Ping timeout: 264 seconds]
camus1 has joined #linux-rockchip
kaspter has quit [Ping timeout: 260 seconds]
camus1 is now known as kaspter
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 260 seconds]
kevery1 is now known as kevery
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 264 seconds]
kevery1 is now known as kevery
field^Mop has joined #linux-rockchip
field^Zzz4 has quit [Ping timeout: 272 seconds]
kevery1 has joined #linux-rockchip
kevery has quit [Read error: Connection reset by peer]
kevery1 is now known as kevery
gendevbot has quit [Ping timeout: 260 seconds]
gendevbot has joined #linux-rockchip
s_frit has quit [Remote host closed the connection]
s_frit has joined #linux-rockchip
vstehle has joined #linux-rockchip
camus1 has joined #linux-rockchip
kaspter has quit [Ping timeout: 256 seconds]
camus1 is now known as kaspter
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 264 seconds]
kevery1 is now known as kevery
kevery has quit [Remote host closed the connection]
kevery has joined #linux-rockchip
ldevulder has joined #linux-rockchip
camus1 has joined #linux-rockchip
kaspter has quit [Ping timeout: 256 seconds]
camus1 is now known as kaspter
damex has quit [Ping timeout: 256 seconds]
leah2 has joined #linux-rockchip
damex has joined #linux-rockchip
matthias_bgg has joined #linux-rockchip
matthias_bgg has quit [Ping timeout: 264 seconds]
alpernebbi has joined #linux-rockchip
stikonas has joined #linux-rockchip
vicencb has joined #linux-rockchip
kaspter has quit [Ping timeout: 272 seconds]
kaspter has joined #linux-rockchip
nlhowell has joined #linux-rockchip
indy has quit [Read error: No route to host]
indy has joined #linux-rockchip
matthias_bgg has joined #linux-rockchip
lkcl has quit [Ping timeout: 258 seconds]
lkcl has joined #linux-rockchip
kaspter has quit [Ping timeout: 272 seconds]
kaspter has joined #linux-rockchip
kaspter has quit [Remote host closed the connection]
damex has quit [Read error: Connection reset by peer]
damex has joined #linux-rockchip
alpernebbi has quit [Remote host closed the connection]
alpernebbi has joined #linux-rockchip
kaspter has joined #linux-rockchip
wens has joined #linux-rockchip
kaspter has quit [Remote host closed the connection]
kaspter has joined #linux-rockchip
matthias_bgg has quit [Ping timeout: 272 seconds]
matthias_bgg has joined #linux-rockchip
<mmind00>
ukleinek: no problems, just didn't get to it yet
<mmind00>
ukleinek: hopefully do more patches this week
<ukleinek>
mmind00: ok, fine
<mmind00>
ukleinek: I just had half an hour to kill yesterday and grabbed some easy ones
<ukleinek>
mmind00: I was just a bit <insertadjectivehere>, because I got prompt responses when my patch set was still non-optimal and input just stopped for my v4.
<mmind00>
ukleinek: there was a bit much work and "holidays" involved the last weeks
<ukleinek>
mmind00: known problem, I was just surprised by the hard edge
<ukleinek>
mmind00: if you come around to look after my patch, don't forget to add Rob's ack as he promised the maintainer will care for :-)
<mmind00>
ukleinek: :-D thanks for that pointer
JohnDoe_71Rus has joined #linux-rockchip
<ukleinek>
mmind00: that was a trick. I assume you will decide you will only remember this when you pick up my patch set immediately. :-P
<mmind00>
ukleinek: :-P you assumed correctly
<mmind00>
ukleinek: I just instructed b4 to get you series
<ukleinek>
\o/
<robmur01>
heh, isn't that how reviewing normally goes? First couple of versions you can skim and point out enough obvious issues in 5 minutes; by about v5 you end up having to budget about half a day to cross-check documentation or other implementations, going back to recall reasoning from previous rounds, etc. to convince yourself it's really right
<robmur01>
at least that's how it tends to go for me :D
<mmind00>
robmur01: it's especially fun when the patch touches parts that don't change often .... still need to look at clock patches
<robmur01>
I think there's a couple of series in my inbox that are at about v12 and I hardly dare even look at because there goes most of the rest of the week :P
<ukleinek>
robmur01: with my reviewer hat on I'm sometimes annoyed about myself that I failed to point out stuff in v1 that is unchanged up to (say) v4.
<ukleinek>
so I think doing a careful review for v1 might beneficial for both sides.
* ukleinek
adds a verb into the last sentence
<mmind00>
ukleinek: homework ... please do a follow up patch updating Documentation/devicetree/bindings/arm/rockchip.yaml ;-)
* ukleinek
tries to find out how this file is sorted
<ukleinek>
ah, description
<ukleinek>
mmind00: do you prefer a completely new patch, or a fixup!?
<mmind00>
new patch ... I already applied the other 2 ;-)
<ukleinek>
ok
<mmind00>
ukleinek: i.e. in general we have (1) vendor prefix, (2) binding-doc in rockchip.yaml (3) dts ... so that patch was just missing when you post it, we can wait a bit for Robs Ack ... but he said in the past there is no need for a simple compatible