From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Daniel Schultz <d.schultz@phytec.de>,
Openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] cryptodev: Fix build errors with v4.11
Date: Sun, 28 Jan 2018 10:21:30 +0000 [thread overview]
Message-ID: <1517134890.3090.0.camel@linuxfoundation.org> (raw)
In-Reply-To: <1516984865-2976-1-git-send-email-d.schultz@phytec.de>
On Fri, 2018-01-26 at 17:41 +0100, Daniel Schultz wrote:
> Commit message from the included patch:
> "Linux kernel has added -Werror=designated-init around 4.11
> (c834f0e8a8b)
> triggering build errors with gcc 5 and 6 (but not with gcc 4)"
>
> Backport from https://github.com/cryptodev-linux/cryptodev-linux
> Based on commit f0d69774afb27ffc62bf353465fba145e70cb85a
>
> Signed-off-by: Daniel Schultz <d.schultz@phytec.de>
> Acked-by: California Sullivan <california.l.sullivan@intel.com>
> ---
> .../cryptodev/cryptodev-module_1.9.bb | 1 +
> .../0001-ioctl.c-Fix-build-with-linux-4.13.patch | 49
> ++++++++++++++++++++++
> 2 files changed, 50 insertions(+)
> create mode 100644 meta/recipes-kernel/cryptodev/files/0001-ioctl.c-
> Fix-build-with-linux-4.13.patch
This merged 10 days ago:
http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=1e5e38f1e7f09dd12a24e62142da747c760ce0c3
?
Cheers,
Richrd
next prev parent reply other threads:[~2018-01-28 10:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-26 16:41 [PATCH] cryptodev: Fix build errors with v4.11 Daniel Schultz
2018-01-26 17:02 ` ✗ patchtest: failure for " Patchwork
2018-01-28 10:21 ` Richard Purdie [this message]
2018-01-29 8:30 ` [PATCH] " Daniel Schultz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1517134890.3090.0.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=Openembedded-core@lists.openembedded.org \
--cc=d.schultz@phytec.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.