08:58 <arnd> NishanthMenon: I'm not exactly sure what you are asking, though it's probably fine. What exactly do you want to allow?

08:59 <arnd> nathanchance: I uploaded gcc-13.2.0 binaries. I could not figure out how it decides on the set of headers to install for plugin, but I managed to reproduce the problem and added the missing file by hand, which seems to work but is not ideal

09:42 <pivi> arnd: NishanthMenon concerns is that dt-bindings update get merged from some specific subsystem tree, so unless we wait one whole release cycles, we will have some binding check failing in TI trees, while next would be fine.

09:42 <pivi> for example this: bb410c03b999 ("dt-bindings: net: can: Remove interrupt properties for MCAN") is in next

09:42 <pivi> and 108f61e03963 ("arm64: dts: ti: k3-am62: Add MCU MCAN nodes") is in TI tree

09:43 <pivi> the commit in the TI tree would not pass the DT checker without bb410c03b999

09:43 <pivi> I assume this is fine, since next is fine, and everything will be fine in the coming -rc1

10:20 <arnd> yes, that works for me

10:21 <arnd> I don't want to see normal build warning (gcc or dtc) get merged as part of the normal branches, and I require these to be clean, but I'm not enforcing the dtbs_check warnings for anyone at the moment

12:03 <NishanthMenon> Thanks arnd

12:04 <NishanthMenon> Thanks pivi .