lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 23 Sep 2014 15:59:51 -0700 From: ashutosh dixit <ashutosh.dixit@...el.com> To: Randy Dunlap <rdunlap@...radead.org> Cc: "linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>, "linux-doc\@vger.kernel.org" <linux-doc@...r.kernel.org>, Andrew Morton <akpm@...ux-foundation.org>, Peter Foley <pefoley2@...oley.com>, "Dutt\, Sudeep" <sudeep.dutt@...el.com>, "Rao\, Nikhil" <nikhil.rao@...el.com>, Greg Kroah-Hartman <gregkh@...uxfoundation.org> Subject: Re: [PATCH linux-next] Documentation: mic: mpssd: Disable mpssd builds for kernels < 3.13 On Tue, Sep 23 2014 at 02:46:10 PM, Randy Dunlap <rdunlap@...radead.org> wrote: > On 09/23/14 14:55, Ashutosh Dixit wrote: >> mpssd depends on headers available in kernels >= 3.13. Therefore >> disable the build for kernels < 3.13. For kernels < 3.13, to avoid the >> appearance of a build break simply print an error message and exit. > > Why is this needed? This file won't be built in any automated build > in v3.13 or any kernel until v3.17 at the earliest? > Correct, if things in Documentation will be compiled against the headers in the kernel source tree then this patch is not required. However, Andrew had reported the following compile error: > In file included from Documentation/mic/mpssd/sysfs.c:21: > Documentation/mic/mpssd/mpssd.h:55:30: error: linux/virtio_ids.h: No such file or directory which made it appear to us that Documentation was being compiled against headers installed on the system, not headers in the kernel source tree. The patch was submitted to address this latter case, but if that does not occur it is not required. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists