From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: stable@vger.kernel.org
Subject: Re: 4.14-stable-queue build failure
Date: Tue, 21 Aug 2018 07:07:13 +0200 [thread overview]
Message-ID: <20180821050713.GA22851@kroah.com> (raw)
In-Reply-To: <20180820212453.ribz6icxozqvbmar@debian>
On Mon, Aug 20, 2018 at 10:24:53PM +0100, Sudip Mukherjee wrote:
> Hi Greg,
>
> My build is failing with v4.14.65 + stable queue patches.
> It fails with the error:
>
> sound/core/seq/seq_clientmgr.c: In function ‘snd_seq_poll’:
> sound/core/seq/seq_clientmgr.c:1100:10: error: ‘EPOLLERR’ undeclared (first use in this function)
> return EPOLLERR;
> ^~~~~~~~
Yeah, I see that (other trees are also broken.) I tried to take Sunday
and Monday off, but no... :)
Anyway, I'll fix this up late tonight or tomorrow morning, I'm traveling
all today.
thanks,
greg k-h
next prev parent reply other threads:[~2018-08-21 8:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-20 21:24 4.14-stable-queue build failure Sudip Mukherjee
2018-08-21 5:07 ` Greg Kroah-Hartman [this message]
2018-08-21 5:35 ` 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=20180821050713.GA22851@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.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).