ChanServ changed the topic of #armlinux to: ARM kernel talk [Upstream kernel, find your vendor forums for questions about their kernels] | https://libera.irclog.whitequark.org/armlinux
System_Error has quit [Remote host closed the connection]
lain6141 has quit [Read error: Connection reset by peer]
lain6141 has joined #armlinux
lain6141 has quit [Changing host]
lain6141 has joined #armlinux
monstr has joined #armlinux
heat has joined #armlinux
amitk has joined #armlinux
monstr has quit [Ping timeout: 252 seconds]
frieder has joined #armlinux
gclement has joined #armlinux
apritzel has joined #armlinux
apritzel has quit [Ping timeout: 256 seconds]
headless has joined #armlinux
sszy has joined #armlinux
amitk has quit [Ping timeout: 268 seconds]
prabhakalad has quit [Quit: Konversation terminated!]
prabhakalad has joined #armlinux
heat has quit [Remote host closed the connection]
heat has joined #armlinux
Livio has joined #armlinux
apritzel has joined #armlinux
Livio has quit [Ping timeout: 268 seconds]
atorgue1 has joined #armlinux
atorgue has quit [Read error: Connection reset by peer]
atorgue__ has joined #armlinux
atorgue1 has quit [Read error: Connection reset by peer]
heat_ has joined #armlinux
heat has quit [Read error: Connection reset by peer]
gclement has quit [Quit: Leaving.]
robmur01 has quit [Remote host closed the connection]
gclement has joined #armlinux
robmur01 has joined #armlinux
gclement has quit [Ping timeout: 246 seconds]
headless has quit [Quit: Konversation terminated!]
gclement has joined #armlinux
<geertu>
arnd: Apparently you still merged the e-fuse DT bindings (commit 24c7b96472179f16 ("Merge tag 'renesas-dt-bindings-for-v6.11-tag1' ...), which were dropped in the v2 PR.
gclement has quit [Ping timeout: 272 seconds]
System_Error has quit [Ping timeout: 260 seconds]
<geertu>
arnd: Probably not too bad, I can update them with nvmem subnodes when that support is being written ;-)
gclement has joined #armlinux
<arnd>
geertu: right, my mistake. I only noticed the driver as a problem and marked that branch accordingly but failed to notice that it was also referenced in the dt-bindings branch. I agree it's fine to fix it up later along with the final driver
atorgue__ has quit [Read error: Connection reset by peer]
atorgue1 has quit [Read error: Connection reset by peer]
atorgue1 has joined #armlinux
atorgue__ has joined #armlinux
atorgue has quit [Read error: Connection reset by peer]
atorgue1 has quit [Read error: Connection reset by peer]
Livio has joined #armlinux
atorgue1 has joined #armlinux
atorgue has joined #armlinux
atorgue__ has quit [Read error: Connection reset by peer]
atorgue1 has quit [Read error: Connection reset by peer]
<marc|gonzalez>
broonie: commits e4222bbdecf4a5d5c25df753e9f5aefd96368ae3 & 9174fd60e55d7ff1ad2c909c67de48ebe7008e5a appear to be the same patch. How is it possible to have the same patch twice in the same git tree?
heat has quit [Remote host closed the connection]
heat has joined #armlinux
<geertu>
marc|gonzalez: Different branches
<marc|gonzalez>
geertu: why would a maintainer apply the same commit to different branches? because there is more stuff based on that base patch different in the 2 branches?
<geertu>
marc|gonzalez: Might be a mistake. Or rebasing a branch and merging it again.
<marc|gonzalez>
also, maintainers submit more than 1 branch to torvalds?
<militantorc>
hi
System_Error has quit [Remote host closed the connection]
<geertu>
marc|gonzalez: Usually the same commit is only submitted once to Linus, even when present in multiple branches (i.e. both based on a shared immutable branch)
<geertu>
So most probably just a silly mistake or rebase issue
<militantorc>
Time to study boot.img
<geertu>
Using --pretty=fuller shows there was just 47s between the two commits, so I guess broonie rebased a branch after merging in into another long-lived branch.
System_Error has joined #armlinux
<broonie>
Or the patch was in two different series and I didn't notice.
<marc|gonzalez>
broonie: but if you apply two series to the same branch, git would omit the second occurrence
<broonie>
But if they're applied on separate branches...
<marc|gonzalez>
the second occurrence ... of an identical patch included in both series
<marc|gonzalez>
broonie: some maintainers submit multiple branches to torvalds?
<broonie>
a) yes b) not all merge requests have a simple linear history, some have merge commits in them.
<marc|gonzalez>
I did not know that. Thanks
<marc|gonzalez>
I have lived in the warm & safe confines of "fast forward only merges"
<militantorc>
So I gained a bit more understanding and clarity now
<militantorc>
So the .img file I booted from to twrp is basically what is called in android a 'boot.img' file. I also have my phones official firmware boot.img file, so I guess in theory if I can modify and repack that boot.img I can probably change the fstab and other things
<marc|gonzalez>
su & suid are similar but different concepts. There probably is a channel more focused on what you're asking about, I'm just not quite sure where to point you to. Maybe one of the XDA channels?
<militantorc>
does that exist on libera
<marc|gonzalez>
are you recompiling your firmware?
<marc|gonzalez>
I'm thinking a LineageOS channel might be a good starting point?
<militantorc>
marc|gonzalez, i don't have the sources. as i common with many phon makers, this one is a gpl violator
gclement2 has joined #armlinux
gclement1 has quit [Quit: Leaving.]
gclement1 has joined #armlinux
gclement has quit [Ping timeout: 268 seconds]
<marc|gonzalez>
militantorc: try #lineageos maybe? They make AOSP-based FW for lots of Android devices.