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
arnd has quit [*.net *.split]
jkridner has quit [*.net *.split]
j`ey has quit [*.net *.split]
pivi has quit [*.net *.split]
Crofton has quit [*.net *.split]
TheCoffeMaker_ has quit [*.net *.split]
olofj has quit [*.net *.split]
mag has quit [*.net *.split]
Crofton has joined #armlinux
olofj has joined #armlinux
j`ey has joined #armlinux
jkridner has joined #armlinux
mag has joined #armlinux
arnd has joined #armlinux
pivi has joined #armlinux
TheCoffeMaker has joined #armlinux
mraynal has quit [Remote host closed the connection]
mraynal has joined #armlinux
apritzel has quit [Ping timeout: 246 seconds]
mag_ has joined #armlinux
cambrian_invader has quit [Server closed connection]
cambrian_invader has joined #armlinux
jclsn has quit [Ping timeout: 246 seconds]
jclsn has joined #armlinux
sakman_ is now known as sakman
sakman_ has joined #armlinux
sakman has quit [Ping timeout: 255 seconds]
broonie has quit [Server closed connection]
broonie has joined #armlinux
ezulian has joined #armlinux
cbeznea has joined #armlinux
ezulian has quit [Ping timeout: 245 seconds]
amitk has joined #armlinux
apritzel has joined #armlinux
vigneshr has quit [Server closed connection]
vigneshr has joined #armlinux
apritzel has quit [Ping timeout: 258 seconds]
frieder has joined #armlinux
mripard has joined #armlinux
nsaenz has quit [Remote host closed the connection]
nsaenz has joined #armlinux
prabhakarlad has quit [Quit: Client closed]
nsaenz has quit [Ping timeout: 255 seconds]
prabhakarlad has joined #armlinux
sszy has joined #armlinux
luispm has quit [Ping timeout: 246 seconds]
nsaenz has joined #armlinux
monstr has joined #armlinux
griffinp has joined #armlinux
luispm has joined #armlinux
monstr has quit [Ping timeout: 255 seconds]
amitk_ has joined #armlinux
amitk_ has quit [Remote host closed the connection]
rgallaispou has quit [Remote host closed the connection]
rgallaispou has joined #armlinux
nsaenz_ has joined #armlinux
headless has joined #armlinux
nsaenz has quit [Ping timeout: 246 seconds]
apritzel has joined #armlinux
monstr has joined #armlinux
sszy has quit [Ping timeout: 258 seconds]
CounterPillow has quit [Server closed connection]
CounterPillow has joined #armlinux
monstr has quit [Ping timeout: 260 seconds]
griffinp has quit [Ping timeout: 258 seconds]
prabhakarlad has quit [Quit: Client closed]
nsaenz_ has quit [Remote host closed the connection]
nsaenz has joined #armlinux
sszy has joined #armlinux
griffinp has joined #armlinux
prabhakarlad has joined #armlinux
biju has joined #armlinux
sakman_ is now known as sakman
headless has quit [Quit: Konversation terminated!]
amitk has quit [Ping timeout: 260 seconds]
apritzel has quit [Remote host closed the connection]
apritzel has joined #armlinux
cbeznea_ has joined #armlinux
cbeznea has quit [Ping timeout: 260 seconds]
cbeznea has joined #armlinux
cbeznea_ has quit [Ping timeout: 258 seconds]
headless has joined #armlinux
monstr has joined #armlinux
griffinp has quit [Ping timeout: 258 seconds]
torez has joined #armlinux
sakman has quit [Ping timeout: 258 seconds]
palmer has joined #armlinux
<palmer>
ardb: there was an arm64 update to libstub in the riscv KASLR patch set, so I had a merge conflict. I think I got it right (just adding the new EFI_ALLOC_LIMIT arg to efi_random_alloc())
headless has quit [Quit: Konversation terminated!]
griffinp has joined #armlinux
frieder has quit [Remote host closed the connection]
rgallaispou has quit [Read error: Connection reset by peer]
<ukleinek>
tlwoerner: usually the arm-soc people have their trees in next. Note that next is currently "closed" as it only should contain patches targeting v6.6-rc1
<broonie>
tlwoerner: You should probably have sent that to soc@kernel.org, they weren't in CC and since it's not split out by submaintainer none of them will have been likely to individually apply.
<broonie>
(and the subject line being odd means the subarch maintainers are likely to have ignored it)
<tlwoerner>
ah okay, i thought linux-arm-kernel was the right place. i cc'ed each arch individually. thanks
<tlwoerner>
any advice on what i should do next? should i wait for the next cycle and just send the arm patch?
<ukleinek>
tlwoerner: use "ARM: defconfig: " as a prefix for a new submission round
Lucanis has quit [Ping timeout: 246 seconds]
prabhakarlad has quit [Quit: Client closed]
monstr has quit [Remote host closed the connection]
<tlwoerner>
sounds good
nsaenz_ has joined #armlinux
Lucanis has joined #armlinux
nsaenz has quit [Ping timeout: 245 seconds]
<ardb>
palmer: you can just tell linus about the merge conflict and how to resolve it, no?
<ardb>
he tends to prefer that over merging stuff from the merge window into your tree before sending it
<broonie>
tlwoerner: In general look at the git log and try to follow a similar pattern to whatever is there.
amitk has joined #armlinux
prabhakarlad has joined #armlinux
sagar20 has joined #armlinux
prabhakarlad has quit [Client Quit]
nsaenz_ has quit [Remote host closed the connection]
prabhakarlad has joined #armlinux
nsaenz has joined #armlinux
prabhakar has joined #armlinux
Esmil has quit [Server closed connection]
Esmil has joined #armlinux
<palmer>
ardb: it was between stuff already in linus/master and the new stuff in that patch set, I usually resolve those locally -- either as an actual merge (like here), or just when rebasing the patch. I think to do this differently I'd have to send this as its own PR?
<palmer>
or I guess not have moved my base branch for the merge window, but I was picking up stuff late because of dependencies
<broonie>
palmer: Linus generally just wants you to tell him that the conflict exists and let him figure it out.
<palmer>
broonie: OK, I guess I just always do all the merging and send a single PR. So in this case it sounds like I should send two?
cbeznea_ has joined #armlinux
<broonie>
palmer: Just send one with a note about the conflict.
cbeznea_ has quit [Client Quit]
<palmer>
broonie: then the conflict's already resolved, though
<broonie>
Do these new patches depend on or conflict with the stuff in master?
<palmer>
broonie: ya. We split out a shared routine from arm64, but that got a fix
<broonie>
palmer: So which is it - dependency or conflict?
sukrutb_ has joined #armlinux
<palmer>
broonie: a conflict
<broonie>
So is there a conflict or isn't there? To repeat, the general thing is to send the pull request and just note any special handling it'll need.
<javierm>
ukleinek: hi, yes I can pick through drm-misc tomorrow all from that set that already have an ack, except the i915 because they have their own devel tree
ezulian has joined #armlinux
amitk has quit [Remote host closed the connection]
ezulian has quit [Ping timeout: 246 seconds]
nsaenz_ has joined #armlinux
nsaenz has quit [Ping timeout: 258 seconds]
nsaenz_ has quit [Ping timeout: 258 seconds]
biju has quit [Quit: Konversation terminated!]
cbeznea has quit [Ping timeout: 246 seconds]
apritzel_ has joined #armlinux
<ukleinek>
javierm: 👍
<headless>
hmm... does zero division cause a kernel oops on arm?
<headless>
or just pr_err() and dump_stack()?
* headless
strongly suspects there's no division insn on classic arm but not sure abouyt aargh64
<headless>
:-)
* headless
sees sdiv and udiv in ARM ARM
<phh>
it was optional up to ARM11, but I'm pretty sure it's mandatory since ARMv7-A
<robmur01>
off the top of my head, I think SDIV/UDIV are mandatory on v7-R, and v7-A with the virtualisation extensions, but e.g. Cortex-A9 doesn't have them
<robmur01>
and there is no divide by zero exception
<headless>
robmur01: well defined? isn't 0 a result of 0 by non-0 division?
<headless>
+dividing
sakman has joined #armlinux
<robmur01>
the pseudocode says that if operand2 is 0 then result is 0, *otherwise* it actually does a mathematical division
<robmur01>
hence it is defined
<broonie>
ie, it's defined in the architecture not in mathematics.
<robmur01>
indeed I was already thinking within the implied context of an Arm instruction, rather than abstract mathematics in general :D
<ardb>
palmer: if the conflict is resolved, it means your branch is based on changes that appeared in linus's tree after v6.5
* broonie
suspects that palmer might mean it's resolved in mainline already as a result of the arm64 changes which had the same commit/conflict having been merged but I'm not clear.
<headless>
g'nite
headless has quit [Quit: Konversation terminated!]