Messages in this thread | | | From | "Li, Philip" <> | Subject | RE: [PATCH 0/3] RISC-V: A few build/warning fixes and cleanup | Date | Thu, 1 Nov 2018 02:19:11 +0000 |
| |
> Subject: Re: [PATCH 0/3] RISC-V: A few build/warning fixes and cleanup > > CC Philip, current kbuild test robot maintainer. > > On Wed, Oct 31, 2018 at 12:12:21PM -0600, Logan Gunthorpe wrote: > > > >On 2018-10-31 11:52 a.m., Olof Johansson wrote: > >> I've migrated machines to a new system and that CI is up and running. > >> Right now the emails don't go anywhere but me, but let me know where > >> you want them sent and I'll be happy to do so (probably not > >> linux-riscv due to volume/noise). They're also uploaded to > >> http://arm-soc.lixom.net/buildlogs/riscv/. > >> > >> Since you keep single-patch branches in your tree, and I compile > >> everything for every branch, I've restricted what branches I poll and > >> build. Right now it's "for*" and "riscv*". > > > >I think it would also be very nice to get the existing kbuild test robot > >to start compile testing a few riscv configs. It already does most of thanks Logan, the support to riscv and nds32 has been in our TODO list for a while, but whole team is blocked by other effort. We will focus on this soon to complete it within 2-3 weeks.
> >the other arches. This would help us catch these kinds of issues even > >earlier seeing that test robot tests patches on mailing lists and many > >other repos before Palmer would even pull them into his branch. > >(Including a repo I routinely push branches to before sending out patches.) > > > >I'm not sure who's currently responsible for the robot but I've copied > >Fenguang who, I believe, set it up originally as well as the kbuild > >lists. Hopefully he can point us in the right direction to help get this > >set up. > > > >Thanks, > > > >Logan > >
| |