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
rvalue has quit [Ping timeout: 264 seconds]
rvalue has joined #armlinux
apritzel has quit [Ping timeout: 264 seconds]
tiagom has quit [Quit: WeeChat 4.2.1]
jclsn has quit [Ping timeout: 256 seconds]
jclsn has joined #armlinux
Lockesmith has quit [Remote host closed the connection]
Lockesmith has joined #armlinux
jn has quit [Ping timeout: 256 seconds]
jn has joined #armlinux
jn has joined #armlinux
heat has quit [Ping timeout: 246 seconds]
amitk has joined #armlinux
gfernandez has joined #armlinux
shenki has quit [Ping timeout: 260 seconds]
shenki has joined #armlinux
gfernandez has quit [Quit: Client closed]
gfernandez has joined #armlinux
cbeznea_ has joined #armlinux
rvalue has quit [Ping timeout: 252 seconds]
rvalue has joined #armlinux
TheCoffeMaker has quit [Quit: So long and thanks for all the fish]
gfernandez has quit [Quit: Client closed]
gfernandez has joined #armlinux
iivanov has joined #armlinux
bjoto` has joined #armlinux
monstr has joined #armlinux
bjoto has quit [Ping timeout: 260 seconds]
iivanov has quit [Remote host closed the connection]
iivanov has joined #armlinux
apritzel has joined #armlinux
SystemError has quit [Ping timeout: 255 seconds]
apritzel has quit [Ping timeout: 255 seconds]
SystemError has joined #armlinux
ezulian has joined #armlinux
gfernandez has quit [Quit: Client closed]
nsaenz has joined #armlinux
biju has joined #armlinux
prabhakar has quit [Quit: Connection closed]
gfernandez has joined #armlinux
headless has joined #armlinux
nact has quit [Ping timeout: 272 seconds]
prabhakar has joined #armlinux
prabhakalad has joined #armlinux
prabhakalad has quit [Client Quit]
prabhakalad has joined #armlinux
gclement has joined #armlinux
nact has joined #armlinux
socksinspace has quit [Ping timeout: 256 seconds]
mripard has joined #armlinux
gclement has quit [Ping timeout: 256 seconds]
alpernebbi has quit [Ping timeout: 256 seconds]
bjoto` has quit [Remote host closed the connection]
gclement has joined #armlinux
mvaittin has joined #armlinux
apritzel_ has joined #armlinux
bjoto has joined #armlinux
headless has quit [Quit: Konversation terminated!]
alpernebbi has joined #armlinux
sszy has joined #armlinux
gfernandez has quit [Quit: Client closed]
ezulian has quit [Quit: ezulian]
gfernandez has joined #armlinux
<conchuod>
ukleinek: your name is breaking b4 for me :)
<CounterPillow>
Is b4 struggling with umlauts or what?
<conchuod>
I have to wonder if it is environment related though. It reproduced on two of my machines but I doubt that this is a problem for everyone given how many patches Uwe submits.
<ukleinek>
conchuod: usually b4 handles this just fine
<CounterPillow>
python3 shouldn't depend on the braindead mess that is locales to do UTF-8 so I wonder how it could be your environment, unless it shells out into something locale-dependant for generating the e-mail
<ukleinek>
conchuod: not knowing what you do, but the result of b4 am 20240226033945.816974-1-jisheng.teoh@starfivetech.com looks good on my side
<conchuod>
b4 am looks fine, its b4 ty where it cocks up
<ukleinek>
ah, I don't use that and won't try it on a mail I didn't apply :-)
<conchuod>
ty doesn't actually send the emails (at least not be default)
<conchuod>
It just writes out all of the ty emails to disk so you can send them with send-email
<ukleinek>
maybe I'm the wrong person to give feedback because for me it takes that funny name out of the Cc: field
TheCoffeMaker has joined #armlinux
<conchuod>
Heh, this does not reproduce consistently. Time to larp as an ostrich for a while!
<geertu>
conchuod: Content-Transfer-Encoding: 8bit vs. 7bit?
<conchuod>
Ah I see something that I had missed. I thought I pasted the b4 output, but actually that .thanks file is modified as soon as you call send-email, and I got confused about the reproducibility.
<conchuod>
geertu: I tried modifying the thanks letter to have 8bit before calling send-email but same result.
bjoto has quit [Remote host closed the connection]
bjoto has joined #armlinux
dmart has joined #armlinux
<conchuod>
Perhaps not a b4 problem but rather send-email itself Hmmge
nsaenz has quit [Remote host closed the connection]
psydroid has joined #armlinux
gfernandez has quit [Quit: Client closed]
gfernandez has joined #armlinux
<marc|gonzalez>
robher: krzk: is it allowed to write opp-hz = /bits/ 64 <100000000>; instead of opp-hz = <0> <100000000>; ?
<krzk>
marc|gonzalez: don't understand. `git grep opp-hz` and you see everywhere first syntax.
<krzk>
so how could it be not allowed if everyone is using this?
heat has joined #armlinux
<marc|gonzalez>
because of the million times I used the same thing everyone was using, and a maintainer told me "you're not allowed to use this" ?
<krzk>
then I don't understand the question...
<marc|gonzalez>
I'll rephrase (but I think you answered already)
<marc|gonzalez>
If "/bits/ 64 <100000000>" and "<0> <100000000>;" are equivalent (I think they are), is one preferred over the other?
<krzk>
they are not equivalent, second has a syntax error and suggests two items, but first has only one item.
ezulian has joined #armlinux
<krzk>
opp-hz is only 64-bit, so second should not be allowed, unbless you meant <0 100000000> ?
TheCoffeMaker has quit [Quit: So long and thanks for all the fish]
<marc|gonzalez>
right I meant <0 100000000> sorry
<krzk>
marc|gonzalez: then they should be equivalent. I don't know if /bits/ notable going to be deprecated/explicitly disallowed, but there is no two-tupple syntax variant...
<krzk>
I meant, there are examples of no two-tupple-syntax variants in the bindings or DTS
<krzk>
so kind if everyone will have the same trouble if something changes here
<marc|gonzalez>
OK thanks, I'll keep that in mind
bjoto has quit [Remote host closed the connection]
bjoto has joined #armlinux
<marc|gonzalez>
Personally, I find the syntax <0 N1 0 N2 0 N3> confusing, and would prefer simply writing /bits/ 64 <N1 N2 N3> when dealing with < 2**32 64-bit values
<robher>
marc|gonzalez: All 3 syntaxes are valid and equivalent as they all result in exactly the same byte stream in the DTB. The /bits/ form is certainly the preference.
<marc|gonzalez>
thanks robher & krzk
<marc|gonzalez>
robher: is fw_loaded_by_tee an acceptable name for a boolean property?
<marc|gonzalez>
(for a platform where linux is not authorized to load FW, but must go through the Trusted Execution Environment circus)