From: Brendan Higgins <brendanhiggins@google.com>
To: Patricia Alfonso <trishalfonso@google.com>
Cc: David Gow <davidgow@google.com>,
Andrey Ryabinin <aryabinin@virtuozzo.com>,
Dmitry Vyukov <dvyukov@google.com>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
kasan-dev <kasan-dev@googlegroups.com>,
KUnit Development <kunit-dev@googlegroups.com>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>
Subject: Re: [PATCH v4 1/4] Add KUnit Struct to Current Task
Date: Fri, 3 Apr 2020 10:11:10 -0700 [thread overview]
Message-ID: <CAFd5g45owC+D+K4RuppmyTJ+d+NGRL1CpuciXwXYvmtBfXnXYg@mail.gmail.com> (raw)
In-Reply-To: <20200402204639.161637-4-trishalfonso@google.com>
On Thu, Apr 2, 2020 at 1:46 PM 'Patricia Alfonso' via KUnit
Development <kunit-dev@googlegroups.com> wrote:
>
> In order to integrate debugging tools like KASAN into the KUnit
> framework, add KUnit struct to the current task to keep track of the
> current KUnit test.
>
> Signed-off-by: Patricia Alfonso <trishalfonso@google.com>
Reviewed-by: Brendan Higgins <brendanhiggins@google.com>
next prev parent reply other threads:[~2020-04-03 17:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 20:46 [PATCH v4 0/4] KUnit-KASAN Integration Patricia Alfonso
2020-04-02 20:46 ` [PATCH v4 2/4] KUnit: KASAN Integration Patricia Alfonso
2020-04-03 13:19 ` Andrey Konovalov
2020-04-03 17:17 ` Patricia Alfonso
2020-04-06 17:44 ` Andrey Konovalov
2020-04-03 14:35 ` Alan Maguire
2020-04-02 20:46 ` [PATCH v4 4/4] KASAN: Testing Documentation Patricia Alfonso
2020-04-02 20:46 ` [PATCH v4 1/4] Add KUnit Struct to Current Task Patricia Alfonso
2020-04-03 17:11 ` Brendan Higgins [this message]
2020-04-02 20:46 ` [PATCH v4 3/4] KASAN: Port KASAN Tests to KUnit Patricia Alfonso
2020-04-03 13:39 ` Andrey Konovalov
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=CAFd5g45owC+D+K4RuppmyTJ+d+NGRL1CpuciXwXYvmtBfXnXYg@mail.gmail.com \
--to=brendanhiggins@google.com \
--cc=aryabinin@virtuozzo.com \
--cc=davidgow@google.com \
--cc=dvyukov@google.com \
--cc=juri.lelli@redhat.com \
--cc=kasan-dev@googlegroups.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=trishalfonso@google.com \
--cc=vincent.guittot@linaro.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;
as well as URLs for NNTP newsgroup(s).