From: Shuah Khan <skhan@linuxfoundation.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Brendan Higgins <brendanhiggins@google.com>
Cc: SeongJae Park <sjpark@amazon.com>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
KUnit Development <kunit-dev@googlegroups.com>,
SeongJae Park <sjpark@amazon.de>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v2 3/3] kunit: Introduce get_file_path() helper
Date: Tue, 10 Nov 2020 14:15:09 -0700 [thread overview]
Message-ID: <3d481d6b-c7aa-303b-841a-111aebd55a8e@linuxfoundation.org> (raw)
In-Reply-To: <f3c2de52-5955-6392-6b10-edb4dc4cf231@linuxfoundation.org>
On 11/5/20 10:56 AM, Shuah Khan wrote:
> On 11/5/20 10:28 AM, Andy Shevchenko wrote:
>> On Thu, Nov 05, 2020 at 08:35:16AM -0800, Brendan Higgins wrote:
>>> On Tue, Nov 3, 2020 at 3:24 AM Andy Shevchenko
>>> <andriy.shevchenko@linux.intel.com> wrote:
>>>> 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?
>>>
>>> I'm not actually sure that this qualifies as a fix. I certainly don't
>>> mind if this goes in 5.10, in fact, I would prefer it.
>>>
3/3 will go into 5.11.
>>> In any case, I added it to Shuah's queue. I will leave it up to Shuah
>>> whether it goes in as a fix in 5.10, or needs to wait for the next
>>> merge window.
>>
>> I'm fine with either. My solely concern is that I would like to get
>> this moved
>> forward somehow.
>>
>
> Once the kunit pull request for rc3 clears, I will look at these and
> make a call. This patch series finalized during the merge window,
> hence you are going to see some delays. If it doesn't make the cut
> for fixes, it will go into 5.11
>
Applied 1/3 and 2/3 to
https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git/
kuni-fixes branch.
I will send them up in my next pull request, probably rc5.
thanks,
-- Shuah
next prev parent reply other threads:[~2020-11-10 21:15 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
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 [this message]
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=3d481d6b-c7aa-303b-841a-111aebd55a8e@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=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 \
/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