<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Feb 2, 2016 at 1:40 PM, Saul Wold <span dir="ltr">&lt;<a href="mailto:sgw@linux.intel.com" target="_blank">sgw@linux.intel.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Tue, 2016-02-02 at 20:05 +0200, Alexandru But wrote:<br>
&gt; nvme uapi header was renamed from nvme.h to nvme_ioctl.h in linux<br>
&gt; 4.4, but the<br>
&gt; header list was not updated. This causes efivar (and maybe other)<br>
&gt; package build<br>
&gt; to fail. This should fix the build while the commit is backported in<br>
&gt; the<br>
&gt; kernel.<br>
&gt;<br>
</span>Would it not make more sense to fix efivar (and maybe others) instead<br>
of changing the kernel headers, which were clearly changed for a reason<br>
to start with.<br></blockquote><div><br></div><div>Yep. But I recall some argument against that. I&#39;m on a plane at the moment<br></div><div>and can&#39;t check my references.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
This patch seems to be pending: <br>
<a href="https://gitweb.gentoo.org/repo/gentoo.git/tree/sys-libs/efivar/files/0.
21-nvme_ioctl.h.patch" rel="noreferrer" target="_blank">https://gitweb.gentoo.org/repo/gentoo.git/tree/sys-libs/efivar/files/0.<br>
21-nvme_ioctl.h.patch</a><br>
<br>
And a more appropriate patch to the kernel headers would be backporting<br>
this already merged patch:<br>
<br>
<a href="https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/
?id=a9cf8284b45110a4d98aea180a89c857e53bf850" rel="noreferrer" target="_blank">https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/<br>
?id=a9cf8284b45110a4d98aea180a89c857e53bf850</a><br>
<br>
You can request that Bruce (the linux-yocto maintainer) backport this<br>
patch via the <a href="mailto:linux-yocto@yoctoproject.org">linux-yocto@yoctoproject.org</a> list.<br>
<br></blockquote><br></div><div class="gmail_quote">Maybe I&#39;m missing something, but wouldn&#39;t that just fix projects that build against<br></div><div class="gmail_quote">linux-yocto ? If that&#39;s good enough, then yes, I can cherry pick the patch (or<br></div><div class="gmail_quote">better yet, get it via -stable).<br><br></div><div class="gmail_quote">but we&#39;d still need to update the linux-libc-headers, since unless these apps<br></div><div class="gmail_quote">are building against the kernel_staging_dir, they are using the libc-headers<br></div><div class="gmail_quote">variant of the header. <br><br></div><div class="gmail_quote">Right ? .. or again, I may be missing what efivar is building against.<br></div><div class="gmail_quote"><br></div><div class="gmail_quote">Bruce<br></div><div class="gmail_quote"><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Sau!<br>
<div class="HOEnZb"><div class="h5"> <br>
&gt; Signed-off-by: Alexandru But &lt;<a href="mailto:alexandru.but@ni.com">alexandru.but@ni.com</a>&gt;<br>
&gt; ---<br>
&gt;  ...i-update-install-list-after-nvme.h-rename.patch | 34<br>
&gt; ++++++++++++++++++++++<br>
&gt;  .../linux-libc-headers/<a href="http://linux-libc-headers_4.4.bb" rel="noreferrer" target="_blank">linux-libc-headers_4.4.bb</a>   |  4 +++<br>
&gt;  2 files changed, 38 insertions(+)<br>
&gt;  create mode 100644 meta/recipes-kernel/linux-libc-headers/linux-<br>
&gt; libc-headers/0001-uapi-update-install-list-after-nvme.h-rename.patch<br>
&gt;<br>
&gt; diff --git a/meta/recipes-kernel/linux-libc-headers/linux-libc-<br>
&gt; headers/0001-uapi-update-install-list-after-nvme.h-rename.patch<br>
&gt; b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers/0001-<br>
&gt; uapi-update-install-list-after-nvme.h-rename.patch<br>
&gt; new file mode 100644<br>
&gt; index 0000000..4d9f5a1<br>
&gt; --- /dev/null<br>
&gt; +++ b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers/0001-<br>
&gt; uapi-update-install-list-after-nvme.h-rename.patch<br>
&gt; @@ -0,0 +1,34 @@<br>
&gt; +From a9cf8284b45110a4d98aea180a89c857e53bf850 Mon Sep 17 00:00:00<br>
&gt; 2001<br>
&gt; +From: Mike Frysinger &lt;<a href="mailto:vapier@gentoo.org">vapier@gentoo.org</a>&gt;<br>
&gt; +Date: Sun, 10 Jan 2016 20:14:11 -0500<br>
&gt; +Subject: [PATCH] uapi: update install list after nvme.h rename<br>
&gt; +<br>
&gt; +Commit 9d99a8dda154 (&quot;nvme: move hardware structures out of the uapi<br>
&gt; +version of nvme.h&quot;) renamed nvme.h to nvme_ioctl.h, but the uapi<br>
&gt; list<br>
&gt; +still refers to nvme.h.  People trying to install the headers hit a<br>
&gt; +failure as the header no longer exists.<br>
&gt; +<br>
&gt; +Cc: <a href="mailto:stable@vger.kernel.org">stable@vger.kernel.org</a><br>
&gt; +Signed-off-by: Mike Frysinger &lt;<a href="mailto:vapier@gentoo.org">vapier@gentoo.org</a>&gt;<br>
&gt; +Reviewed-by: Christoph Hellwig &lt;<a href="mailto:hch@lst.de">hch@lst.de</a>&gt;<br>
&gt; +Signed-off-by: Jens Axboe &lt;<a href="mailto:axboe@fb.com">axboe@fb.com</a>&gt;<br>
&gt; +---<br>
&gt; + include/uapi/linux/Kbuild | 2 +-<br>
&gt; + 1 file changed, 1 insertion(+), 1 deletion(-)<br>
&gt; +<br>
&gt; +diff --git a/include/uapi/linux/Kbuild b/include/uapi/linux/Kbuild<br>
&gt; +index 628e6e6..88e1292 100644<br>
&gt; +--- a/include/uapi/linux/Kbuild<br>
&gt; ++++ b/include/uapi/linux/Kbuild<br>
&gt; +@@ -306,7 +306,7 @@ header-y += nfs_mount.h<br>
&gt; + header-y += nl80211.h<br>
&gt; + header-y += n_r3964.h<br>
&gt; + header-y += nubus.h<br>
&gt; +-header-y += nvme.h<br>
&gt; ++header-y += nvme_ioctl.h<br>
&gt; + header-y += nvram.h<br>
&gt; + header-y += omap3isp.h<br>
&gt; + header-y += omapfb.h<br>
&gt; +--<br>
&gt; +2.6.1<br>
&gt; +<br>
&gt; diff --git a/meta/recipes-kernel/linux-libc-headers/linux-libc-<br>
&gt; <a href="http://headers_4.4.bb" rel="noreferrer" target="_blank">headers_4.4.bb</a> b/meta/recipes-kernel/linux-libc-headers/linux-libc-<br>
&gt; <a href="http://headers_4.4.bb" rel="noreferrer" target="_blank">headers_4.4.bb</a><br>
&gt; index 3763dc0..c8c7a10 100644<br>
&gt; --- a/meta/recipes-kernel/linux-libc-headers/linux-libc-<br>
&gt; <a href="http://headers_4.4.bb" rel="noreferrer" target="_blank">headers_4.4.bb</a><br>
&gt; +++ b/meta/recipes-kernel/linux-libc-headers/linux-libc-<br>
&gt; <a href="http://headers_4.4.bb" rel="noreferrer" target="_blank">headers_4.4.bb</a><br>
&gt; @@ -5,5 +5,9 @@ SRC_URI_append_libc-musl = &quot;\<br>
&gt;      file://0002-libc-compat.h-prevent-redefinition-of-struct-<br>
&gt; ethhdr.patch \<br>
&gt;      file://0003-remove-inclusion-of-sysinfo.h-in-kernel.h.patch \<br>
&gt;     &quot;<br>
&gt; +SRC_URI_append =&quot;\<br>
&gt; +    file://0001-uapi-update-install-list-after-nvme.h-rename.patch \<br>
&gt; +   &quot;<br>
&gt; +<br>
&gt;  SRC_URI[md5sum] = &quot;9a78fa2eb6c68ca5a40ed5af08142599&quot;<br>
&gt;  SRC_URI[sha256sum] =<br>
&gt; &quot;401d7c8fef594999a460d10c72c5a94e9c2e1022f16795ec51746b0d165418b2&quot;<br>
&gt; --<br>
&gt; 2.6.1<br>
&gt;<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature">&quot;Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end&quot;</div>
</div></div>