NishanthMenon changed the topic of #linux-ti to: Linux development for TI SoCs | Logs: https://libera.irclog.whitequark.org/linux-ti/| paste logs in https://pastebin.ubuntu.com/ | Let it rock! Vendor SDK/kernel: Also see e2e.ti.com
rob_w has joined #linux-ti
Pali has joined #linux-ti
DeVector[m] has quit [Quit: Bridge terminating on SIGTERM]
tomba has quit [Quit: Bridge terminating on SIGTERM]
ikarso has joined #linux-ti
ecdhe has quit [Ping timeout: 268 seconds]
ecdhe has joined #linux-ti
Kubu_work has joined #linux-ti
florian has joined #linux-ti
florian_kc has joined #linux-ti
tomba has joined #linux-ti
DeVector[m] has joined #linux-ti
florian_kc has quit [Ping timeout: 256 seconds]
florian_kc has joined #linux-ti
Kubu_work has quit [Ping timeout: 264 seconds]
ladis has quit [Remote host closed the connection]
ladis has joined #linux-ti
rob_w has quit [Remote host closed the connection]
Kubu_work has joined #linux-ti
Kubu_work has quit [Quit: Leaving.]
florian_kc has quit [Ping timeout: 264 seconds]
florian has quit [Quit: Ex-Chat]
<vigneshr> Hi arnd , We have quite a large number of DT fixes (~42 patches) which are related to dts W=12 and dtbs_checks related fixes across multiple K3 SoCs... There are couple patches that add new nodes (timers, and i2cs) which make it possible to sync / use Kernel dts files in u-boot. Hope that's okay for -rc2/-rc3 pull request. Patch queue is here: https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git/log/?h=ti-k3-dts-next
ikarso has quit [Quit: Connection closed for inactivity]
florian_kc has joined #linux-ti
<arnd> vigneshr: it's a bit much, and I can't always tell from a single patch what the purpose is. Maybe split into two branches and send both pull requests together
<arnd> the warning fixes should be no problem, just put them all into one branch. I would generally recommend listing the warning output (or an abbreviated form if it's long) in the changelog text to clarify that it addresses a warning
<arnd> for the new nodes, the rule is to have those in the merge window. I can make exceptions if there is a good reason, but those need to be explained well in the changelog text
<arnd> the main concern on my end is how I can write my own pull request with a sensible justification to torvalds and summarize the contents of the combined fixes branch that I send, so anything that makes my life easier in that helps
Kubu_work has joined #linux-ti
Kubu_work has quit [Quit: Leaving.]
Kubu_work has joined #linux-ti
Kubu_work has quit [Client Quit]
Kubu_work has joined #linux-ti
Kubu_work has quit [Client Quit]
Kubu_work has joined #linux-ti
Pali has quit [Quit: Pali]
Kubu_work has quit [Quit: Leaving.]
florian_kc has quit [Ping timeout: 246 seconds]