On Thu, Apr 16, 2020 at 2:34 AM Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> wrote: > > Hi Dmitry, > > On Tue, 14 Apr 2020 13:12:50 +0200 Dmitry Vyukov <dvyukov@xxxxxxxxxx> wrote: > > > > AI: we need to CC linux-next@ on linux-next build/boot failures. I > > will work on this. > > We have functionality to CC given emails on _all_ bugs on the given > > tree, but we don't have this for build/boot bugs only. I will try to > > add this soon. > > Stephen, do you want to be CCed as well? Or just linux-next@? > > Please cc me as well, thanks. To close the loop: I implemented and deployed 2 improvements: 1. Notion of per-repo "build maintainers": https://github.com/google/syzkaller/commit/88cb3e92ba25303ab67aaceb083fe7304fccd32f Now linux-next@ and Stephen should be CCed on all linux-next breakages automatically. 2. Finding maintainers for build errors: https://github.com/google/syzkaller/commit/65a44e22ba217ef7272b9d3735e9d12cfaa204f6 syzbot will attempt to extract the broken file name from make output and then run get_matainers.pl on it to find relevant emails.
