On Fri, Jan 27, 2023 at 11:50 PM Andy Shevchenko <andriy.shevchenko@xxxxxxxxx> wrote: > > On Fri, Jan 27, 2023 at 04:41:37PM +0200, Andy Shevchenko wrote: > > On Fri, Jan 27, 2023 at 11:31:07PM +0900, Masahiro Yamada wrote: > > > On Fri, Jan 27, 2023 at 10:25 PM Andy Shevchenko > > > <andriy.shevchenko@xxxxxxxxx> wrote: > > > > > > > > On Thu, Dec 29, 2022 at 04:43:10PM +0900, Masahiro Yamada wrote: > > > > > The top .gitignore comments about how to detect files breaking > > > > > .gitignore rules, but people rarely care about it. > > > > > > > > > > Add a new W=1 warning to detect files that are tracked but ignored by > > > > > git. If git is not installed or the source tree is not tracked by git > > > > > at all, this script does not print anything. > > > > > > > > > > Running it on v6.2-rc1 detected the following: > > > > > > > > Since patch was published there is no sign it was ever meet Linux Next. > > > > What's the plan? > > > > > > Oh? > > > > Sorry, my mistake. I need to understand why these patches do not fix > > the issue I have. > > OK, after carefully reading the commit message it's actually the culprit of > the warnings I have. > > So, it seems we need to wait maintainers / developers of the respective code > to go and fix this. Is it your intention? Yes. I expect the 0day bot will block new breakages, but actually the mainline got more warnings under kselftest. -- Best Regards Masahiro Yamada
