From: Greg KH <gregkh@linuxfoundation.org>
To: Lei Chen <chenl.lei@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
torvalds@linux-foundation.org, stable@vger.kernel.org,
lwn@lwn.net, Jiri Slaby <jslaby@suse.cz>
Subject: Re: Linux 4.4.128
Date: Mon, 16 Apr 2018 12:10:07 +0200 [thread overview]
Message-ID: <20180416101007.GA17839@kroah.com> (raw)
In-Reply-To: <CAB5AJuW_09u4kRAM9qj3M05QvZSkcbhDa-CeOC=nxUNt8FU20Q@mail.gmail.com>
On Mon, Apr 16, 2018 at 05:58:26PM +0800, Lei Chen wrote:
> Hi Greg,
> This release has build failure on file tools/perf/tests/code-reading.c:
>
> tests/code-reading.c: In function ‘read_object_code’:
> tests/code-reading.c:186:19: error: ‘KMOD_DECOMP_LEN’ undeclared
> (first use in this function)
> char decomp_name[KMOD_DECOMP_LEN];
> ^
Thanks for the info, I'm going to revert the offending patch from the
next release.
greg k-h
prev parent reply other threads:[~2018-04-16 10:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 20:24 Linux 4.4.128 Greg KH
2018-04-13 20:24 ` Greg KH
2018-04-16 9:58 ` Lei Chen
2018-04-16 10:10 ` 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=20180416101007.GA17839@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=chenl.lei@gmail.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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).