From: keescook at chromium.org (Kees Cook)
Subject: [PATCH 1/6] selftests: Extract single-test shell logic from lib.mk
Date: Tue, 23 Apr 2019 19:43:58 -0700 [thread overview]
Message-ID: <CAGXu5jLgaU-Q1hxn0aSpbDsAbHNxmriCQ5inSajUKUUez4PpLg@mail.gmail.com> (raw)
In-Reply-To: <ca4605d5-9423-542e-5a10-2b681293baf9@kernel.org>
On Tue, Apr 23, 2019 at 3:47 PM shuah <shuah at kernel.org> wrote:
> You can see it by running
>
> make summary=1 TARGETS="breakpoints" kselftest
Okay, thanks for this! I'll give it a spin.
> with and without your first patch. Ca you fix the regression and send
> me revised patches. Sorry, I didn't get back to you sooner. A few bugs
> I found kept me busy.
>
> While I was testing your patch series, I found test build failures due
> to circular dependency that needed fixing. In addition, the same
> headers_install dependency, also broke O= and KBUILD_OUTPUT builds
> and fixed those as well. Long story short, these fixes might conflict
> with your work.
I can rebase the series -- which tree should I look at? (Is it all in
-next already?)
Thanks!
--
Kees Cook
WARNING: multiple messages have this Message-ID (diff)
From: keescook@chromium.org (Kees Cook)
Subject: [PATCH 1/6] selftests: Extract single-test shell logic from lib.mk
Date: Tue, 23 Apr 2019 19:43:58 -0700 [thread overview]
Message-ID: <CAGXu5jLgaU-Q1hxn0aSpbDsAbHNxmriCQ5inSajUKUUez4PpLg@mail.gmail.com> (raw)
Message-ID: <20190424024358.h07C8YQ1pD0Z5esrRq7L7aKepluqnodE7q673vLYTQ0@z> (raw)
In-Reply-To: <ca4605d5-9423-542e-5a10-2b681293baf9@kernel.org>
On Tue, Apr 23, 2019@3:47 PM shuah <shuah@kernel.org> wrote:
> You can see it by running
>
> make summary=1 TARGETS="breakpoints" kselftest
Okay, thanks for this! I'll give it a spin.
> with and without your first patch. Ca you fix the regression and send
> me revised patches. Sorry, I didn't get back to you sooner. A few bugs
> I found kept me busy.
>
> While I was testing your patch series, I found test build failures due
> to circular dependency that needed fixing. In addition, the same
> headers_install dependency, also broke O= and KBUILD_OUTPUT builds
> and fixed those as well. Long story short, these fixes might conflict
> with your work.
I can rebase the series -- which tree should I look at? (Is it all in
-next already?)
Thanks!
--
Kees Cook
next prev parent reply other threads:[~2019-04-24 2:43 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 23:55 [PATCH 0/6] selftests: Move test output to diagnostic lines keescook
2019-04-09 23:55 ` Kees Cook
2019-04-09 23:55 ` [PATCH 1/6] selftests: Extract single-test shell logic from lib.mk keescook
2019-04-09 23:55 ` Kees Cook
2019-04-16 23:11 ` shuah
2019-04-16 23:11 ` shuah
2019-04-16 23:16 ` keescook
2019-04-16 23:16 ` Kees Cook
2019-04-16 23:21 ` shuah
2019-04-16 23:21 ` shuah
2019-04-23 22:31 ` keescook
2019-04-23 22:31 ` Kees Cook
2019-04-23 22:47 ` shuah
2019-04-23 22:47 ` shuah
2019-04-24 2:43 ` keescook [this message]
2019-04-24 2:43 ` Kees Cook
2019-04-24 2:46 ` shuah
2019-04-24 2:46 ` shuah
2019-04-09 23:55 ` [PATCH 2/6] selftests: Use runner.sh for emit targets keescook
2019-04-09 23:55 ` Kees Cook
2019-04-09 23:55 ` [PATCH 3/6] selftests: Extract logic for multiple test runs keescook
2019-04-09 23:55 ` Kees Cook
2019-04-09 23:55 ` [PATCH 4/6] selftests/runner: Add plan line and fix result line syntax keescook
2019-04-09 23:55 ` Kees Cook
2019-04-09 23:55 ` [PATCH 5/6] selftests/runner: Distinguish between missing and non-executable keescook
2019-04-09 23:55 ` Kees Cook
2019-04-09 23:55 ` [PATCH 6/6] selftests: Move test output to diagnostic lines keescook
2019-04-09 23:55 ` 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=CAGXu5jLgaU-Q1hxn0aSpbDsAbHNxmriCQ5inSajUKUUez4PpLg@mail.gmail.com \
--to=unknown@example.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 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.