From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: stable <stable@vger.kernel.org>
Subject: Re: Build failures in v3.18.y-stable-queue
Date: Fri, 29 Dec 2017 10:19:29 +0100 [thread overview]
Message-ID: <20171229091929.GH18441@kroah.com> (raw)
In-Reply-To: <b2d7aa9f-9ff1-440c-4efd-4eaf19fb24a4@roeck-us.net>
On Thu, Dec 28, 2017 at 07:47:28AM -0800, Guenter Roeck wrote:
> Building arm:allmodconfig (and others) ... failed
> --------------
> Error log:
> /opt/buildbot/slave/stable-queue-3.18/build/drivers/mfd/cros_ec_spi.c:26:8: error: expected '=', ',', ';', 'asm' or '__attribute__' before '->' token
>
> The file (and the patch changing it) is messed up.
Yeah, something went really wrong, I'll work on it on Monday.
thanks,
greg k-h
next prev parent reply other threads:[~2017-12-29 9:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-28 15:47 Build failures in v3.18.y-stable-queue Guenter Roeck
2017-12-29 9:19 ` Greg Kroah-Hartman [this message]
2017-12-30 15:29 ` Greg Kroah-Hartman
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=20171229091929.GH18441@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux@roeck-us.net \
--cc=stable@vger.kernel.org \
/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).