From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: SeongJae Park <sjpark@amazon.com>
Cc: linux-kselftest@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>,
kunit-dev@googlegroups.com, SeongJae Park <sjpark@amazon.de>,
Brendan Higgins <brendanhiggins@google.com>
Subject: Re: [PATCH v2 3/3] kunit: Introduce get_file_path() helper
Date: Tue, 3 Nov 2020 13:25:12 +0200 [thread overview]
Message-ID: <20201103112512.GZ4077@smile.fi.intel.com> (raw)
In-Reply-To: <20201028092915.8053-1-sjpark@amazon.com>
On Wed, Oct 28, 2020 at 10:29:15AM +0100, SeongJae Park wrote:
> On Mon, 26 Oct 2020 18:59:27 +0200 Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
>
> > Helper allows to derive file names depending on --build_dir argument.
> >
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > Reviewed-by: Brendan Higgins <brendanhiggins@google.com>
> > Tested-by: Brendan Higgins <brendanhiggins@google.com>
>
> Reviewed-by: SeongJae Park <sjpark@amazon.de>
Thanks!
Brendan, Shuah, can we get this series applied, please?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2020-11-03 11:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 16:59 [PATCH v2 1/3] kunit: Do not pollute source directory with generated files (.kunitconfig) Andy Shevchenko
2020-10-26 16:59 ` [PATCH v2 2/3] kunit: Do not pollute source directory with generated files (test.log) Andy Shevchenko
2020-10-26 16:59 ` [PATCH v2 3/3] kunit: Introduce get_file_path() helper Andy Shevchenko
[not found] ` <20201028092915.8053-1-sjpark@amazon.com>
2020-11-03 11:25 ` Andy Shevchenko [this message]
2020-11-05 16:35 ` Brendan Higgins
2020-11-05 17:28 ` Andy Shevchenko
2020-11-05 17:56 ` Shuah Khan
2020-11-10 21:15 ` Shuah Khan
2020-11-11 17:19 ` Andy Shevchenko
2020-10-30 19:50 ` [PATCH v2 1/3] kunit: Do not pollute source directory with generated files (.kunitconfig) Andy Shevchenko
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=20201103112512.GZ4077@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=brendanhiggins@google.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=sjpark@amazon.com \
--cc=sjpark@amazon.de \
--cc=skhan@linuxfoundation.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