From: Alexander Alemayhu <alexander@alemayhu.com>
To: Sumit Semwal <sumit.semwal@linaro.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
shuah@kernel.org, LKML <linux-kernel@vger.kernel.org>,
stable@vger.kernel.org, linux-kselftest@vger.kernel.org,
Brian Norris <computersforpeace@gmail.com>,
mcgrof@kernel.org, Kees Cook <keescook@chromium.org>
Subject: Re: LTS testing with latest kselftests - some failures
Date: Fri, 16 Jun 2017 01:05:03 +0200 [thread overview]
Message-ID: <20170615230503.GB3071@gmail.com> (raw)
In-Reply-To: <CAO_48GFNXyqTDN85y8FKLV3wj19JJ28sWXuX4Vex3LVzaxzGCw@mail.gmail.com>
On Thu, Jun 15, 2017 at 11:26:53PM +0530, Sumit Semwal wrote:
>
> 4. bpf tests: These seem to have build failures in mainline as well -
> I also tried to build kselftest-next, but a simple 'make -C
> tools/testing/selftests/bpf' seems to error out. Are there any special
> instructions to build these? [I tried x86_64, arm64 cross-compile on x86_64]
>
Do you have the full failure output? If you haven't already you might
also want to run 'make headers_install' in the top level directory.
--
Mit freundlichen Grüßen
Alexander Alemayhu
WARNING: multiple messages have this Message-ID (diff)
From: Alexander Alemayhu <alexander@alemayhu.com>
To: Sumit Semwal <sumit.semwal@linaro.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
shuah@kernel.org, LKML <linux-kernel@vger.kernel.org>,
stable@vger.kernel.org, linux-kselftest@vger.kernel.org,
Brian Norris <computersforpeace@gmail.com>,
mcgrof@kernel.org, Kees Cook <keescook@chromium.org>
Subject: Re: LTS testing with latest kselftests - some failures
Date: Fri, 16 Jun 2017 01:05:03 +0200 [thread overview]
Message-ID: <20170615230503.GB3071@gmail.com> (raw)
In-Reply-To: <CAO_48GFNXyqTDN85y8FKLV3wj19JJ28sWXuX4Vex3LVzaxzGCw@mail.gmail.com>
On Thu, Jun 15, 2017 at 11:26:53PM +0530, Sumit Semwal wrote:
>
> 4. bpf tests: These seem to have build failures in mainline as well -
> I also tried to build kselftest-next, but a simple 'make -C
> tools/testing/selftests/bpf' seems to error out. Are there any special
> instructions to build these? [I tried x86_64, arm64 cross-compile on x86_64]
>
Do you have the full failure output? If you haven't already you might
also want to run 'make headers_install' in the top level directory.
--
Mit freundlichen Gr��en
Alexander Alemayhu
next prev parent reply other threads:[~2017-06-15 23:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-15 17:56 LTS testing with latest kselftests - some failures Sumit Semwal
2017-06-15 18:30 ` Shuah Khan
2017-06-15 23:05 ` Alexander Alemayhu [this message]
2017-06-15 23:05 ` Alexander Alemayhu
2017-06-16 4:31 ` Sumit Semwal
2017-06-16 7:14 ` Alexander Alemayhu
2017-06-16 7:14 ` Alexander Alemayhu
2017-06-16 7:38 ` Sumit Semwal
2017-06-16 19:26 ` Alexander Alemayhu
2017-06-16 19:26 ` Alexander Alemayhu
2017-06-16 16:46 ` Luis R. Rodriguez
2017-06-16 19:29 ` Greg Kroah-Hartman
2017-06-16 19:47 ` Luis R. Rodriguez
2017-06-17 4:16 ` Greg Kroah-Hartman
2017-06-19 14:48 ` Luis R. Rodriguez
2017-06-19 14:55 ` Greg Kroah-Hartman
2017-06-19 17:32 ` Luis R. Rodriguez
2017-06-16 23:55 ` Fengguang Wu
2017-06-19 18:56 ` Kees Cook
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=20170615230503.GB3071@gmail.com \
--to=alexander@alemayhu.com \
--cc=computersforpeace@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.org \
--cc=sumit.semwal@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.