From: Greg KH <greg@kroah.com>
To: "A. Wilcox" <awilfox@adelielinux.org>
Cc: stable@vger.kernel.org, adelie-devel@lists.adelielinux.org,
Timothy Pearson <tpearson@raptorengineering.com>,
horst@adelielinux.org, gentoo-powerpc@lists.gentoo.org
Subject: Re: [4.14] powerpc: Always initialize input array when calling epapr_hypercall()
Date: Fri, 1 Mar 2019 07:59:03 +0100 [thread overview]
Message-ID: <20190301065903.GA6782@kroah.com> (raw)
In-Reply-To: <2c0741ae-85bc-4b4b-8122-daa749c4a95f@adelielinux.org>
On Thu, Feb 28, 2019 at 05:27:45PM -0600, A. Wilcox wrote:
> Kernel 4.14 fails to build with GCC 8 on powerpc64, due to 'in' being
> uninitialised in epapr_hypercall*.
>
> This is fixed in commit 186b8f1587c79c2fa04bfa392fdf08 upstream, and
> this commit applies cleanly to the 4.14 tree. This commit is already on
> the 4.19 branch.
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2019-03-01 6:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 23:27 [4.14] powerpc: Always initialize input array when calling epapr_hypercall() A. Wilcox
2019-03-01 6:59 ` Greg KH [this message]
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=20190301065903.GA6782@kroah.com \
--to=greg@kroah.com \
--cc=adelie-devel@lists.adelielinux.org \
--cc=awilfox@adelielinux.org \
--cc=gentoo-powerpc@lists.gentoo.org \
--cc=horst@adelielinux.org \
--cc=stable@vger.kernel.org \
--cc=tpearson@raptorengineering.com \
/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;
as well as URLs for NNTP newsgroup(s).