From: Sasha Levin <sashal@kernel.org>
To: Daniel Latypov <dlatypov@google.com>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Zeal Robot <zealci@zte.com.cn>, Lv Ruyi <lv.ruyi@zte.com.cn>,
Brendan Higgins <brendanhiggins@google.com>,
Shuah Khan <skhan@linuxfoundation.org>,
linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com
Subject: Re: [PATCH AUTOSEL 5.17 089/135] kunit: bail out of test filtering logic quicker if OOM
Date: Sun, 5 Jun 2022 09:26:43 -0400 [thread overview]
Message-ID: <YpyvEyomrPpj3JJR@sashalap> (raw)
In-Reply-To: <CAGS_qxrtZBrpk8x64oj53o4EEUCgTj1c4D12W+6UNArQfiiXaQ@mail.gmail.com>
On Tue, May 31, 2022 at 09:15:11AM -0700, Daniel Latypov wrote:
>On Mon, May 30, 2022 at 6:36 AM Sasha Levin <sashal@kernel.org> wrote:
>>
>> From: Daniel Latypov <dlatypov@google.com>
>>
>> [ Upstream commit a02353f491622e49c7ddedc6a6dc4f1d6ed2150a ]
>>
>
>Is it possible to make sure the fix for this commit gets picked up as well [1]?
>I was waiting a bit to see if it was going to get picked up
>automatically, but I don't see such an email yet:
>https://lore.kernel.org/stable/?q=kunit+OOM
>(Perhaps the automation just hasn't gotten around to it yet?)
I'll make sure the fix added along with this commit.
--
Thanks,
Sasha
next prev parent reply other threads:[~2022-06-05 13:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220530133133.1931716-1-sashal@kernel.org>
2022-05-30 13:29 ` [PATCH AUTOSEL 5.17 005/135] selftests/bpf: Fix vfs_link kprobe definition Sasha Levin
2022-05-30 13:29 ` [PATCH AUTOSEL 5.17 006/135] selftests/bpf: Fix parsing of prog types in UAPI hdr for bpftool sync Sasha Levin
2022-05-30 13:30 ` [PATCH AUTOSEL 5.17 089/135] kunit: bail out of test filtering logic quicker if OOM Sasha Levin
2022-05-31 16:15 ` Daniel Latypov
2022-06-05 13:26 ` Sasha Levin [this message]
2022-06-06 15:41 ` Daniel Latypov
2022-05-30 13:31 ` [PATCH AUTOSEL 5.17 111/135] kunit: tool: make parser stop overwriting status of suites w/ no_tests Sasha Levin
2022-05-30 13:31 ` [PATCH AUTOSEL 5.17 126/135] selftests/bpf: Add missing trampoline program type to trampoline_count test Sasha Levin
2022-05-30 13:31 ` [PATCH AUTOSEL 5.17 134/135] selftests/bpf: fix btf_dump/btf_dump due to recent clang change Sasha Levin
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=YpyvEyomrPpj3JJR@sashalap \
--to=sashal@kernel.org \
--cc=brendanhiggins@google.com \
--cc=dlatypov@google.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lv.ruyi@zte.com.cn \
--cc=skhan@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=zealci@zte.com.cn \
/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