Re: [linus:master] BUILD REGRESSION 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e

2017-09-18 Thread Philip Li
On Sun, Sep 17, 2017 at 08:31:56AM -0700, Linus Torvalds wrote: > Fengguang, > it looks like the kernel build robot _only_ tests the actual rc > kernels, and doesn't bisect down where the error started. hi Linus, the robot will also bisect down the error if issue is found on linus repo. The

Re: [linus:master] BUILD REGRESSION 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e

2017-09-18 Thread Philip Li
On Sun, Sep 17, 2017 at 08:31:56AM -0700, Linus Torvalds wrote: > Fengguang, > it looks like the kernel build robot _only_ tests the actual rc > kernels, and doesn't bisect down where the error started. hi Linus, the robot will also bisect down the error if issue is found on linus repo. The

Re: [linus:master] BUILD REGRESSION 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e

2017-09-17 Thread Fengguang Wu
Hi Linus, On Sun, Sep 17, 2017 at 08:31:56AM -0700, Linus Torvalds wrote: Fengguang, it looks like the kernel build robot _only_ tests the actual rc kernels, and doesn't bisect down where the error started. Nah, that's an illusion. :) It's a per-branch summary report _in addition to_

Re: [linus:master] BUILD REGRESSION 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e

2017-09-17 Thread Fengguang Wu
Hi Linus, On Sun, Sep 17, 2017 at 08:31:56AM -0700, Linus Torvalds wrote: Fengguang, it looks like the kernel build robot _only_ tests the actual rc kernels, and doesn't bisect down where the error started. Nah, that's an illusion. :) It's a per-branch summary report _in addition to_

Re: [linus:master] BUILD REGRESSION 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e

2017-09-17 Thread Linus Torvalds
Fengguang, it looks like the kernel build robot _only_ tests the actual rc kernels, and doesn't bisect down where the error started. Any change that when it notices an error, it would bisect it, like it does for linux-next? Linus On Sat, Sep 16, 2017 at 11:02 PM, kbuild test

Re: [linus:master] BUILD REGRESSION 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e

2017-09-17 Thread Linus Torvalds
Fengguang, it looks like the kernel build robot _only_ tests the actual rc kernels, and doesn't bisect down where the error started. Any change that when it notices an error, it would bisect it, like it does for linux-next? Linus On Sat, Sep 16, 2017 at 11:02 PM, kbuild test

[linus:master] BUILD REGRESSION 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e

2017-09-17 Thread kbuild test robot
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e Linux 4.14-rc1 arch/alpha/include/asm/mmu_context.h:160:24: error: invalid type argument of '->' (have 'int') arch/alpha/include/asm/mmu_context.h:160:2: error: implicit

[linus:master] BUILD REGRESSION 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e

2017-09-17 Thread kbuild test robot
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e Linux 4.14-rc1 arch/alpha/include/asm/mmu_context.h:160:24: error: invalid type argument of '->' (have 'int') arch/alpha/include/asm/mmu_context.h:160:2: error: implicit