> On Sat, Aug 19, 2017 at 02:50:48AM +0100, James Simmons wrote: > > > > > On Fri, Aug 18, 2017 at 03:53:56PM -0700, Greg Kroah-Hartman wrote: > > > > On Sat, Aug 19, 2017 at 02:49:02AM +0800, kbuild test robot wrote: > > > > > tree: > > > > > https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git > > > > > staging-testing > > > > > head: 4d64b24f1fd892842e4502c0ff9c0e6b8144efa0 > > > > > commit: 1c4e5aa23a78c16ac15966a7704fa8a6201be095 [306/323] staging: > > > > > lustre: uapi: migrate remaining uapi headers to uapi directory > > > > > > > > Ugh. Let me drop this one, and another uapi one as well from the tree, > > > > hopefully that should fix the build issues... > > > > > > What a mess, am dropping all of the uapi patches now, please fix them up > > > and resend. > > > > > > > No reason to drop them all. Its just a one line fix. I will send right > > away. > > They are now all dropped, sorry, please send a fixed up patch series > that does not break the build at any point in it.
Done. I also updated the patches as [PACTH XX/64 v2] as you requested in the other email. Strange that kbuild didn't see this before the patches landed and that the build breakage was only on one platform. I tested it ever which way possible to make sure its right. One question is how do I run header checker on these UAPI header since they are not in the usually UAPI header path yet. _______________________________________________ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
