From: shuah <shuah@kernel.org>
To: SeongJae Park <sj38.park@gmail.com>, brendanhiggins@google.com
Cc: linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com,
linux-kernel@vger.kernel.org, shuah <shuah@kernel.org>
Subject: Re: [PATCH] kunit: Fix '--build_dir' option
Date: Fri, 6 Sep 2019 09:51:35 -0600 [thread overview]
Message-ID: <3531717b-fa9d-ac94-57ec-0eb501d1ad3b@kernel.org> (raw)
In-Reply-To: <1567771541-7690-1-git-send-email-sj38.park@gmail.com>
On 9/6/19 6:05 AM, SeongJae Park wrote:
> kunit fails to run with '--build_dir' option because the option is not
> properly sent to kernel running procedure. This commit fixes the
> problem.
Can you please include the failure you are seeing in the commit log
thanks,
-- Shuah
next prev parent reply other threads:[~2019-09-06 15:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 12:05 [PATCH] kunit: Fix '--build_dir' option SeongJae Park
2019-09-06 15:51 ` shuah [this message]
2019-09-06 16:11 ` SeongJae Park
2019-09-06 16:11 ` SeongJae Park
2019-09-07 1:16 ` Brendan Higgins
2019-09-07 2:33 ` shuah
2019-09-07 9:08 ` SeongJae Park
2019-10-07 22:03 ` Brendan Higgins
2019-10-07 23:05 ` shuah
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=3531717b-fa9d-ac94-57ec-0eb501d1ad3b@kernel.org \
--to=shuah@kernel.org \
--cc=brendanhiggins@google.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=sj38.park@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