From: Akemi Yagi <toracat@elrepo.org>
To: linux-kernel@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: Linux 4.9.94
Date: Wed, 18 Apr 2018 23:30:22 +0000 (UTC) [thread overview]
Message-ID: <pb8kee$ofo$1@blaine.gmane.org> (raw)
In-Reply-To: <20180413202359.GA22934@kroah.com>
Hi Greg,
This release has the same build failure on file tools/perf/tests/code-
reading.c as the one reported for 4.4.128:
Quoting from https://lkml.org/lkml/2018/4/16/246
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];
The issue on 4.4.128 posted here:
https://lkml.org/lkml/2018/4/14/17
Thanks,
Akemi
prev parent reply other threads:[~2018-04-18 23:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 20:23 Greg KH
2018-04-13 20:24 ` Greg KH
2018-04-18 23:30 ` Akemi Yagi [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='pb8kee$ofo$1@blaine.gmane.org' \
--to=toracat@elrepo.org \
--cc=linux-kernel@vger.kernel.org \
--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
Powered by JetHome