From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Daniel Schultz <d.schultz@phytec.de>,
Openembedded-core@lists.openembedded.org
Subject: Re: [RFC] cryptodev: Fix build errors with v4.11
Date: Fri, 05 Jan 2018 15:25:11 +0000 [thread overview]
Message-ID: <1515165911.30291.31.camel@linuxfoundation.org> (raw)
In-Reply-To: <1515163072-18559-1-git-send-email-d.schultz@phytec.de>
On Fri, 2018-01-05 at 15:37 +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>
I'm a little puzzled. Which release is this against? We're using
kernels newer than 4.11 so why aren't things breaking?
Cheers,
Richard
next prev parent reply other threads:[~2018-01-05 15:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-05 14:37 [RFC] cryptodev: Fix build errors with v4.11 Daniel Schultz
2018-01-05 15:25 ` Richard Purdie [this message]
2018-01-05 15:59 ` Daniel Schultz
2018-01-05 16:33 ` Daniel Schultz
2018-01-17 22:48 ` Cal Sullivan
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=1515165911.30291.31.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox