On Wed, Mar 02, 2016 at 03:29:24AM -0500, Oleg Drokin wrote: > > On Mar 2, 2016, at 2:31 AM, kbuild test robot wrote: > > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git staging-next > > head: 5a9ff74d8e681f9ac6af6cc1444a812b74e7c2de > > commit: caa88c26575c9be856e5a801abd121d7ff0808f8 [1186/1234] staging/lustre: F_SETLKW64 F_SETLK64 F_GETLK64 are always defined > > config: alpha-allmodconfig (attached as .config) > > reproduce: > > wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross > > chmod +x ~/bin/make.cross > > git checkout caa88c26575c9be856e5a801abd121d7ff0808f8 > > # save the attached .config to linux build tree > > make.cross ARCH=alpha > > > > All errors (new ones prefixed by >>): > > > > drivers/staging/lustre/lustre/llite/file.c: In function 'll_file_flock': > >>> drivers/staging/lustre/lustre/llite/file.c:2749:7: error: 'F_SETLKW64' undeclared (first use in this function) > > case F_SETLKW64: > > ^ > > Duh, so alpha does not ever define those and even though there is code in the kernel that uses them unconditionally > (fs/compat.c), it depends on CONFIG_COMPAT that is never defined for alpha (because there was never 32 bit compat there?) > > Anyway, in light of this I guess this patch needs to be reverted then. > > Greg, how do I make that happen, do you want a reversal patch or can you revert it yourself somehow? I've reverted it myself now, so all is fine. greg k-h _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
