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
mraynal has quit [Quit: WeeChat 3.0]
elastic_dog has quit [Ping timeout: 256 seconds]
mraynal has joined #armlinux
elastic_dog has joined #armlinux
apritzel_ has quit [Ping timeout: 240 seconds]
Nact has quit [Ping timeout: 264 seconds]
heat has quit [Ping timeout: 240 seconds]
rvalue has quit [Ping timeout: 240 seconds]
rvalue has joined #armlinux
DrPatater has quit [Quit: Explodes into a thousand pieces]
DrPatater has joined #armlinux
jclsn has quit [Ping timeout: 256 seconds]
jclsn has joined #armlinux
amitk has joined #armlinux
Lucanis0 has quit [Remote host closed the connection]
Lucanis0 has joined #armlinux
Lucanis0 has joined #armlinux
Lucanis0 has quit [Changing host]
luispm has joined #armlinux
macromorgan has quit [Read error: Connection reset by peer]
macromorgan has joined #armlinux
iivanov has joined #armlinux
iivanov has quit [Quit: Leaving.]
iivanov has joined #armlinux
cbeznea has joined #armlinux
monstr has joined #armlinux
<lag>
ukleinek: mfd-for-next-next is a temp branch I use to apply patches to when mfd-for-next has been locked-down prior to the merge-window
<lag>
ukleinek: -next is always okay for any of the subsystems I maintain
<lag>
geertu: Not exactly sure how it would work with worktrees - which I use extensively
amitk has quit [Ping timeout: 268 seconds]
<geertu>
lag: I really should start using worktrees
<geertu>
But I have lots of build trees, so using worktrees I'd have to change the Makefile in the build tree to point to a different worktree all the time.
<lag>
geertu: krzk: ukleinek: ... and now we wait (for the cache to clear) -- https://termbin.com/mm1j
<lag>
geertu: Yes - it's not good for compile_commands.json either
<geertu>
lag: fatal: the remote end hung up unexpectedly ?
<lag>
geertu: However my drive isn't physically large enough to contain different repositories for all of the repos/branches that I work with on daily basis
<lag>
geertu: Yeah, then it went on to push, sooo ??
* lag
shrugs
<geertu>
lag: No alternates?
<lag>
geertu: I have no idea what 'push negotiation' is
<lag>
geertu: I read "proceeding anyway" and get on with something else :)
<lag>
geertu: Now I just need to carve out some time to author something useful !!
<krzk>
lag: geertu: The guide there suggests to do it in your main kernel repo, but as well you can do it via separate repo just for "about" pages. I do it like this to avoid expensive checkouts from full kernel to README one.
<lag>
krzk: The process seems to be orthogonal to worktrees, so I might just author something relevant
<krzk>
lag: yeah, should be fine - you just checkout weird special REF.
<lag>
krzk: Yup, see above
<krzk>
Yes, I saw, it worked :). I am trying to get a talk on plumbers about this and few other tricks. I already had one more case of useful trick few days ago - how to add yourself to LKP/kernel test robot.
<krzk>
Because many folks don't do it or don't know (which is fine hence the need to fly to Richmond :) ).
<lag>
krzk: The Intel one? You just email them and ask.
<geertu>
krzk: Enjoy the holidays (soon)! We'll keep on pestering the new young kid on the DT block instead ;)
<krzk>
lag: Yes, Intel one, although, some longer time ago email-request was politely changed - do it yourself. So you send them pull req. but the point is - people don't know they can have email from test robot with build-success on every branch update.
<lag>
krzk: Glad it was of some use - it's a pain when rebasing though!
<krzk>
yeah, lesson not to rebase :)
<lag>
krzk: During development ...
<tmlind>
so anybody know if the arch/arm/boot/dts subdirectories change is still expected for v6.4-rc cycle or will it be after v6.4-rc1 now?
<tmlind>
i mean after v6.5-rc1 :)
<krzk>
tmlind: this merge window was missed, so I guess we target next one
<tmlind>
krzk: ok makes sense, will send out some pinctrl node name fixes this week then
<tmlind>
hmm i wonder if we should just rename these too: git grep pinmux_ arch/arm64/boot/dts/broadcom/
prabhakarlad has joined #armlinux
headless has joined #armlinux
apritzel has joined #armlinux
iivanov has quit [Quit: Leaving.]
rvalue has quit [Ping timeout: 240 seconds]
headless has quit [Ping timeout: 240 seconds]
headless has joined #armlinux
headless has quit [Client Quit]
headless has joined #armlinux
amitk has joined #armlinux
amitk_ has quit [Ping timeout: 250 seconds]
heat has joined #armlinux
cbeznea1 has joined #armlinux
cbeznea has quit [Ping timeout: 240 seconds]
prabhakarlad has quit [Quit: Client closed]
headless has quit [Quit: Konversation terminated!]
rvalue has joined #armlinux
cbeznea has joined #armlinux
cbeznea1 has quit [Ping timeout: 248 seconds]
iivanov has joined #armlinux
elastic_dog has quit [Remote host closed the connection]
elastic_dog has joined #armlinux
cbeznea1 has joined #armlinux
cbeznea has quit [Ping timeout: 256 seconds]
iivanov has quit [Quit: Leaving.]
<geertu>
lag: You may want to add a .mailmap entry, as the tree has lots of copies of your "Apologies, this mailbox is no longer monitored. Please update your contact information."-address.
<lag>
geertu: I don't see those :D
<lag>
geertu: I will do that too
<krzk>
yeah, nowadays get_maintainers.pl includes addresses from Fixed tags, so it can pick up something old.
<krzk>
Thus the best if everyone add a mailmap
xvmt_ has joined #armlinux
xvmt has quit [Ping timeout: 240 seconds]
xvmt_ is now known as xvmt
headless has joined #armlinux
cbeznea1 has quit [Quit: Leaving.]
cbeznea has joined #armlinux
headless has quit [Quit: Konversation terminated!]