robclark changed the topic of #aarch64-laptops to: Linux support for AArch64 Laptops (Chrome OS Trogdor Devices - Asus NovaGo TP370QL - HP Envy x2 - Lenovo Mixx 630 - Lenovo Yoga C630 - Lenovo ThinkPad X13s - and various other snapdragon laptops) - https://oftc.irclog.whitequark.org/aarch64-laptops
Lucy[m] has joined #aarch64-laptops
quinine has joined #aarch64-laptops
Erisa has quit [Read error: No route to host]
Erisa has joined #aarch64-laptops
wiizzard has joined #aarch64-laptops
szclsya[m] has joined #aarch64-laptops
emily[m] has joined #aarch64-laptops
harvestz[m] has joined #aarch64-laptops
erebionCCCamp232142[m] has joined #aarch64-laptops
strongtz[m] has joined #aarch64-laptops
malvi[m]1 has joined #aarch64-laptops
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
EricCurtin[m] has joined #aarch64-laptops
jenneron[m] has joined #aarch64-laptops
alfredo has joined #aarch64-laptops
Jasper[m] has joined #aarch64-laptops
todi has joined #aarch64-laptops
jhovold has joined #aarch64-laptops
alfredo has quit [Ping timeout: 480 seconds]
<jhovold>
qzed: nios2?! explicitly depending on QCOM_SCM=y should work, but I wonder if QCOM_SCM should really have depends on ARCH_QCOM instead
<jhovold>
there are a bunch bool qcom options that select QCOM_SCM, so I guess it can really only be built in
<jhovold>
unless doing something crazy like the build bot
DocGalaxyBlock[m] has joined #aarch64-laptops
Dylanger has joined #aarch64-laptops
<qzed>
jhovold: hmm yes, I think depends on ARCH_QCOM could make sense, but I guess that's a question for another patchset
<jhovold>
or just include it as a preparatory patch as its clearly needed for your work
<qzed>
I can do that, I'm just thinking about adding the "depends on QCOM_SCM=y" as well because that solves it more directly, without going in some roundabout ways
<jhovold>
but then you get into the question of why QCOM_SCM is tristate in the first place when and can only be built in on qcom platforms, and now you have to sprinkle depends on QCOM_SCM=y all over because of the build bot
<jhovold>
well, the other users do select QCOM_SCM, but i think you get my point
<jhovold>
but yeah, perhaps depends on =y is good enough, the rest can be cleaned up later...
travmurav[m] has joined #aarch64-laptops
<qzed>
hmm yeah
sally[m]1234567 has joined #aarch64-laptops
_[m]1 has joined #aarch64-laptops
mcbridematt has quit [Remote host closed the connection]
Nao[m] has joined #aarch64-laptops
mcbridematt has joined #aarch64-laptops
lun[m] has joined #aarch64-laptops
aigotchi[m] has joined #aarch64-laptops
danielt has joined #aarch64-laptops
saekau[m] has joined #aarch64-laptops
alfredo has joined #aarch64-laptops
alfredo has quit []
EnigmaCurry[m] has joined #aarch64-laptops
alfredo has joined #aarch64-laptops
firlaev-hans-fiete[m] has joined #aarch64-laptops
cenunix[m] has joined #aarch64-laptops
ArtyomK[m] has joined #aarch64-laptops
mcbridematt has quit [Remote host closed the connection]
alfredo has quit [Quit: alfredo]
Leandro[m]1 has joined #aarch64-laptops
alfredo has joined #aarch64-laptops
alfredo has quit [Ping timeout: 480 seconds]
ajhalaney[m] has joined #aarch64-laptops
matalama has joined #aarch64-laptops
matalama has quit [Quit: Connection closed for inactivity]
systwi_ has quit [Ping timeout: 480 seconds]
systwi has joined #aarch64-laptops
heapify has joined #aarch64-laptops
heapify has quit []
<clover[m]>
Heyyy, looks like jhovold is back from vacation!