From: Steven Rostedt <rostedt@goodmis.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Theodore Y. Ts'o" <tytso@mit.edu>,
Brendan Higgins <brendanhiggins@google.com>,
shuah <shuah@kernel.org>, Frank Rowand <frowand.list@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Kees Cook <keescook@google.com>,
Kieran Bingham <kieran.bingham@ideasonboard.com>,
Luis Chamberlain <mcgrof@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Rob Herring <robh@kernel.org>, Stephen Boyd <sboyd@kernel.org>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
devicetree <devicetree@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
kunit-dev@googlegroups.com,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
linux-nvdimm <linux-nvdimm@lists.01.org>,
linux-um@lists.infradead.org,
Sasha Levin <Alexander.Levin@microsoft.com>,
"Bird, Timothy" <Tim.Bird@sony.com>,
Amir Goldstein <amir73il@gmail.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
Daniel Vetter <daniel@ffwll.ch>, Jeff Dike <jdike@addtoit.com>,
Joel Stanley <joel@jms.id.au>,
Julia Lawall <julia.lawall@lip6.fr>,
Kevin Hilman <khilman@baylibre.com>,
Knut Omang <knut.omang@oracle.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Petr Mladek <pmladek@suse.com>,
Randy Dunlap <rdunlap@infradead.org>,
Richard Weinberger <richard@nod.at>,
David Rientjes <rientjes@google.com>,
wfg@linux.intel.com
Subject: Re: [PATCH v18 00/19] kunit: introduce KUnit, the Linux kernel unit testing framework
Date: Mon, 7 Oct 2019 10:40:48 -0400 [thread overview]
Message-ID: <20191007104048.66ae7e59@gandalf.local.home> (raw)
In-Reply-To: <CAHk-=wjcJxypxUOSF-jc=SQKT1CrOoTMyT7soYzbvK3965JmCA@mail.gmail.com>
On Sun, 6 Oct 2019 10:18:11 -0700
Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Sun, Oct 6, 2019 at 9:55 AM Theodore Y. Ts'o <tytso@mit.edu> wrote:
> >
> > Well, one thing we *can* do is if (a) if we can create a kselftest
> > branch which we know is stable and won't change, and (b) we can get
> > assurances that Linus *will* accept that branch during the next merge
> > window, those subsystems which want to use kself test can simply pull
> > it into their tree.
>
> Yes.
>
> At the same time, I don't think it needs to be even that fancy. Even
> if it's not a stable branch that gets shared between different
> developers, it would be good to just have people do a "let's try this"
> throw-away branch to use the kunit functionality and verify that
> "yeah, this is fairly convenient for ext4".
>
> It doesn't have to be merged in that form, but just confirmation that
> the infrastructure is helpful before it gets merged would be good.
Can't you just create an ext4 branch that has the kselftest-next branch
in it, that you build upon. And push that after the kunit test is
merged?
In the past I've had to rely on other branches in next, and would just
hold two branches myself. One with everything not dependent on the other
developer's branch, and one with the work that was. At the merge
window, I would either merge the two or just send two pull requests
with the two branches.
-- Steve
_______________________________________________
Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org
To unsubscribe send an email to linux-nvdimm-leave@lists.01.org
WARNING: multiple messages have this Message-ID (diff)
From: Steven Rostedt <rostedt@goodmis.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Theodore Y. Ts'o" <tytso@mit.edu>,
Brendan Higgins <brendanhiggins@google.com>,
shuah <shuah@kernel.org>, Frank Rowand <frowand.list@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Kees Cook <keescook@google.com>,
Kieran Bingham <kieran.bingham@ideasonboard.com>,
Luis Chamberlain <mcgrof@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Rob Herring <robh@kernel.org>, Stephen Boyd <sboyd@kernel.org>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
devicetree <devicetree@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
kunit-dev@googlegroups.com,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
linux-nvdimm <linux-nvdimm@lists.01.org>,
linux-um@lists.infradead.org,
Sasha Levin <Alexander.Levin@microsoft.com>,
"Bird, Timothy" <Tim.Bird@sony.com>,
Amir Goldstein <amir73il@gmail.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
Daniel Vetter <daniel@ffwll.ch>, Jeff Dike <jdike@addtoit.com>,
Joel Stanley <joel@jms.id.au>,
Julia Lawall <julia.lawall@lip6.fr>,
Kevin Hilman <khilman@baylibre.com>,
Knut Omang <knut.omang@oracle.com>,
Logan Gunthorpe <logang@deltatee.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Petr Mladek <pmladek@suse.com>,
Randy Dunlap <rdunlap@infradead.org>,
Richard Weinberger <richard@nod.at>,
David Rientjes <rientjes@google.com>,
wfg@linux.intel.com
Subject: Re: [PATCH v18 00/19] kunit: introduce KUnit, the Linux kernel unit testing framework
Date: Mon, 7 Oct 2019 10:40:48 -0400 [thread overview]
Message-ID: <20191007104048.66ae7e59@gandalf.local.home> (raw)
In-Reply-To: <CAHk-=wjcJxypxUOSF-jc=SQKT1CrOoTMyT7soYzbvK3965JmCA@mail.gmail.com>
On Sun, 6 Oct 2019 10:18:11 -0700
Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Sun, Oct 6, 2019 at 9:55 AM Theodore Y. Ts'o <tytso@mit.edu> wrote:
> >
> > Well, one thing we *can* do is if (a) if we can create a kselftest
> > branch which we know is stable and won't change, and (b) we can get
> > assurances that Linus *will* accept that branch during the next merge
> > window, those subsystems which want to use kself test can simply pull
> > it into their tree.
>
> Yes.
>
> At the same time, I don't think it needs to be even that fancy. Even
> if it's not a stable branch that gets shared between different
> developers, it would be good to just have people do a "let's try this"
> throw-away branch to use the kunit functionality and verify that
> "yeah, this is fairly convenient for ext4".
>
> It doesn't have to be merged in that form, but just confirmation that
> the infrastructure is helpful before it gets merged would be good.
Can't you just create an ext4 branch that has the kselftest-next branch
in it, that you build upon. And push that after the kunit test is
merged?
In the past I've had to rely on other branches in next, and would just
hold two branches myself. One with everything not dependent on the other
developer's branch, and one with the work that was. At the merge
window, I would either merge the two or just send two pull requests
with the two branches.
-- Steve
WARNING: multiple messages have this Message-ID (diff)
From: Steven Rostedt <rostedt@goodmis.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Petr Mladek <pmladek@suse.com>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Amir Goldstein <amir73il@gmail.com>,
Brendan Higgins <brendanhiggins@google.com>,
dri-devel <dri-devel@lists.freedesktop.org>,
Sasha Levin <Alexander.Levin@microsoft.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Michael Ellerman <mpe@ellerman.id.au>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
linux-nvdimm <linux-nvdimm@lists.01.org>,
shuah <shuah@kernel.org>, Knut Omang <knut.omang@oracle.com>,
Kieran Bingham <kieran.bingham@ideasonboard.com>,
wfg@linux.intel.com, Joel Stanley <joel@jms.id.au>,
David Rientjes <rientjes@google.com>,
Jeff Dike <jdike@addtoit.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
devicetree <devicetree@vger.kernel.org>,
Linux
Subject: Re: [PATCH v18 00/19] kunit: introduce KUnit, the Linux kernel unit testing framework
Date: Mon, 7 Oct 2019 10:40:48 -0400 [thread overview]
Message-ID: <20191007104048.66ae7e59@gandalf.local.home> (raw)
In-Reply-To: <CAHk-=wjcJxypxUOSF-jc=SQKT1CrOoTMyT7soYzbvK3965JmCA@mail.gmail.com>
On Sun, 6 Oct 2019 10:18:11 -0700
Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Sun, Oct 6, 2019 at 9:55 AM Theodore Y. Ts'o <tytso@mit.edu> wrote:
> >
> > Well, one thing we *can* do is if (a) if we can create a kselftest
> > branch which we know is stable and won't change, and (b) we can get
> > assurances that Linus *will* accept that branch during the next merge
> > window, those subsystems which want to use kself test can simply pull
> > it into their tree.
>
> Yes.
>
> At the same time, I don't think it needs to be even that fancy. Even
> if it's not a stable branch that gets shared between different
> developers, it would be good to just have people do a "let's try this"
> throw-away branch to use the kunit functionality and verify that
> "yeah, this is fairly convenient for ext4".
>
> It doesn't have to be merged in that form, but just confirmation that
> the infrastructure is helpful before it gets merged would be good.
Can't you just create an ext4 branch that has the kselftest-next branch
in it, that you build upon. And push that after the kunit test is
merged?
In the past I've had to rely on other branches in next, and would just
hold two branches myself. One with everything not dependent on the other
developer's branch, and one with the work that was. At the merge
window, I would either merge the two or just send two pull requests
with the two branches.
-- Steve
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Steven Rostedt <rostedt@goodmis.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Theodore Y. Ts'o" <tytso@mit.edu>,
Brendan Higgins <brendanhiggins@google.com>,
shuah <shuah@kernel.org>, Frank Rowand <frowand.list@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Kees Cook <keescook@google.com>,
Kieran Bingham <kieran.bingham@ideasonboard.com>,
Luis Chamberlain <mcgrof@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Rob Herring <robh@kernel.org>, Stephen Boyd <sboyd@kernel.org>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
devicetree <devicetree@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
kunit-dev@googlegroups.com,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
linux-nvdimm <linux-nvdimm@lists.01.org>,
linux-um@lists.infradead.org,
Sasha Levin <Alexander.Levin@microsoft.com>,
"Bird, Timothy" <Tim.Bird@sony.com>,
Amir Goldstein <amir73il@gmail.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
Daniel Vetter <daniel@ffwll.ch>, Jeff Dike <jdike@addtoit.com>,
Joel Stanley <joel@jms.id.au>,
Julia Lawall <julia.lawall@lip6.fr>,
Kevin Hilman <khilman@baylibre.com>,
Knut Omang <knut.omang@oracle.com>,
Logan Gunthorpe <logang@deltatee.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Petr Mladek <pmladek@suse.com>,
Randy Dunlap <rdunlap@infradead.org>,
Richard Weinberger <richard@nod.at>,
David Rientjes <rientjes@google.com>,
wfg@linux.intel.com
Subject: Re: [PATCH v18 00/19] kunit: introduce KUnit, the Linux kernel unit testing framework
Date: Mon, 7 Oct 2019 10:40:48 -0400 [thread overview]
Message-ID: <20191007104048.66ae7e59@gandalf.local.home> (raw)
In-Reply-To: <CAHk-=wjcJxypxUOSF-jc=SQKT1CrOoTMyT7soYzbvK3965JmCA@mail.gmail.com>
On Sun, 6 Oct 2019 10:18:11 -0700
Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Sun, Oct 6, 2019 at 9:55 AM Theodore Y. Ts'o <tytso@mit.edu> wrote:
> >
> > Well, one thing we *can* do is if (a) if we can create a kselftest
> > branch which we know is stable and won't change, and (b) we can get
> > assurances that Linus *will* accept that branch during the next merge
> > window, those subsystems which want to use kself test can simply pull
> > it into their tree.
>
> Yes.
>
> At the same time, I don't think it needs to be even that fancy. Even
> if it's not a stable branch that gets shared between different
> developers, it would be good to just have people do a "let's try this"
> throw-away branch to use the kunit functionality and verify that
> "yeah, this is fairly convenient for ext4".
>
> It doesn't have to be merged in that form, but just confirmation that
> the infrastructure is helpful before it gets merged would be good.
Can't you just create an ext4 branch that has the kselftest-next branch
in it, that you build upon. And push that after the kunit test is
merged?
In the past I've had to rely on other branches in next, and would just
hold two branches myself. One with everything not dependent on the other
developer's branch, and one with the work that was. At the merge
window, I would either merge the two or just send two pull requests
with the two branches.
-- Steve
WARNING: multiple messages have this Message-ID (diff)
From: Steven Rostedt <rostedt@goodmis.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Petr Mladek <pmladek@suse.com>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Amir Goldstein <amir73il@gmail.com>,
Brendan Higgins <brendanhiggins@google.com>,
dri-devel <dri-devel@lists.freedesktop.org>,
Sasha Levin <Alexander.Levin@microsoft.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Michael Ellerman <mpe@ellerman.id.au>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Rob Herring <robh@kernel.org>,
linux-nvdimm <linux-nvdimm@lists.01.org>,
shuah <shuah@kernel.org>, Knut Omang <knut.omang@oracle.com>,
Kieran Bingham <kieran.bingham@ideasonboard.com>,
wfg@linux.intel.com, Joel Stanley <joel@jms.id.au>,
David Rientjes <rientjes@google.com>,
Jeff Dike <jdike@addtoit.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
devicetree <devicetree@vger.kernel.org>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
"Bird, Timothy <Tim.Bird@sony.com>,
linux-um@lists.infradead.org,
Julia Lawall" <julia.lawall@lip6.fr>,
Josh Poimboeuf <jpoimboe@redhat.com>,
kunit-dev@googlegroups.com, "Theodore Y. Ts'o" <tytso@mit.edu>,
Richard Weinberger <richard@nod.at>,
Stephen Boyd <sboyd@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Luis Chamberlain <mcgrof@kernel.org>,
Daniel Vetter <daniel@ffwll.ch>, Kees Cook <keescook@google.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Logan Gunthorpe <logang@deltatee.com>,
Kevin Hilman <khilman@baylibre.com>
Subject: Re: [PATCH v18 00/19] kunit: introduce KUnit, the Linux kernel unit testing framework
Date: Mon, 7 Oct 2019 10:40:48 -0400 [thread overview]
Message-ID: <20191007104048.66ae7e59@gandalf.local.home> (raw)
In-Reply-To: <CAHk-=wjcJxypxUOSF-jc=SQKT1CrOoTMyT7soYzbvK3965JmCA@mail.gmail.com>
On Sun, 6 Oct 2019 10:18:11 -0700
Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Sun, Oct 6, 2019 at 9:55 AM Theodore Y. Ts'o <tytso@mit.edu> wrote:
> >
> > Well, one thing we *can* do is if (a) if we can create a kselftest
> > branch which we know is stable and won't change, and (b) we can get
> > assurances that Linus *will* accept that branch during the next merge
> > window, those subsystems which want to use kself test can simply pull
> > it into their tree.
>
> Yes.
>
> At the same time, I don't think it needs to be even that fancy. Even
> if it's not a stable branch that gets shared between different
> developers, it would be good to just have people do a "let's try this"
> throw-away branch to use the kunit functionality and verify that
> "yeah, this is fairly convenient for ext4".
>
> It doesn't have to be merged in that form, but just confirmation that
> the infrastructure is helpful before it gets merged would be good.
Can't you just create an ext4 branch that has the kselftest-next branch
in it, that you build upon. And push that after the kunit test is
merged?
In the past I've had to rely on other branches in next, and would just
hold two branches myself. One with everything not dependent on the other
developer's branch, and one with the work that was. At the merge
window, I would either merge the two or just send two pull requests
with the two branches.
-- Steve
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
next prev parent reply other threads:[~2019-10-07 14:40 UTC|newest]
Thread overview: 207+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-23 9:02 [PATCH v18 00/19] kunit: introduce KUnit, the Linux kernel unit testing framework Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` [PATCH v18 01/19] kunit: test: add KUnit test runner core Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` [PATCH v18 02/19] kunit: test: add test resource management API Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` [PATCH v18 03/19] kunit: test: add string_stream a std::stream like string builder Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` [PATCH v18 04/19] kunit: test: add assertion printing library Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` [PATCH v18 05/19] kunit: test: add the concept of expectations Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` [PATCH v18 06/19] lib: enable building KUnit in lib/ Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 15:35 ` Stephen Boyd
2019-09-23 15:35 ` Stephen Boyd
2019-09-23 15:35 ` Stephen Boyd
2019-09-23 15:35 ` Stephen Boyd
2019-09-23 15:35 ` Stephen Boyd
2019-09-23 9:02 ` [PATCH v18 07/19] kunit: test: add initial tests Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` [PATCH v18 08/19] objtool: add kunit_try_catch_throw to the noreturn list Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` [PATCH v18 09/19] kunit: test: add support for test abort Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` [PATCH v18 10/19] kunit: test: add tests for kunit " Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` [PATCH v18 11/19] kunit: test: add the concept of assertions Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` [PATCH v18 12/19] kunit: test: add tests for KUnit managed resources Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` [PATCH v18 13/19] kunit: tool: add Python wrappers for running KUnit tests Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` [PATCH v18 14/19] kunit: defconfig: add defconfigs for building " Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` [PATCH v18 15/19] Documentation: kunit: add documentation for KUnit Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 15:47 ` Randy Dunlap
2019-09-23 15:47 ` Randy Dunlap
2019-09-23 15:47 ` Randy Dunlap
2019-09-23 15:47 ` Randy Dunlap
2019-09-23 18:06 ` Brendan Higgins
2019-09-23 18:06 ` Brendan Higgins
2019-09-23 18:06 ` Brendan Higgins
2019-09-23 18:06 ` Brendan Higgins
2019-09-23 18:06 ` Brendan Higgins
2019-09-23 19:49 ` Randy Dunlap
2019-09-23 19:49 ` Randy Dunlap
2019-09-23 19:49 ` Randy Dunlap
2019-09-23 19:49 ` Randy Dunlap
2019-09-23 19:49 ` Randy Dunlap
2019-09-23 21:18 ` shuah
2019-09-23 21:18 ` shuah
2019-09-23 21:18 ` shuah
2019-09-23 21:18 ` shuah
2019-09-23 21:18 ` shuah
2019-09-23 21:30 ` Randy Dunlap
2019-09-23 21:30 ` Randy Dunlap
2019-09-23 21:30 ` Randy Dunlap
2019-09-23 21:30 ` Randy Dunlap
2019-09-23 21:30 ` Randy Dunlap
2019-09-24 0:51 ` Randy Dunlap
2019-09-24 0:51 ` Randy Dunlap
2019-09-24 0:51 ` Randy Dunlap
2019-09-23 9:02 ` [PATCH v18 16/19] MAINTAINERS: add entry for KUnit the unit testing framework Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` [PATCH v18 17/19] kernel/sysctl-test: Add null pointer test for sysctl.c:proc_dointvec() Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` [PATCH v18 18/19] MAINTAINERS: add proc sysctl KUnit test to PROC SYSCTL section Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` [PATCH v18 19/19] kunit: fix failure to build without printk Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-09-23 9:02 ` Brendan Higgins
2019-10-04 21:38 ` [PATCH v18 00/19] kunit: introduce KUnit, the Linux kernel unit testing framework Theodore Y. Ts'o
2019-10-04 21:38 ` Theodore Y. Ts'o
2019-10-04 21:38 ` Theodore Y. Ts'o
2019-10-04 21:38 ` Theodore Y. Ts'o
2019-10-04 21:42 ` Linus Torvalds
2019-10-04 21:42 ` Linus Torvalds
2019-10-04 21:42 ` Linus Torvalds
2019-10-04 21:42 ` Linus Torvalds
2019-10-04 21:59 ` shuah
2019-10-04 21:59 ` shuah
2019-10-04 21:59 ` shuah
2019-10-04 21:59 ` shuah
2019-10-04 21:59 ` shuah
2019-10-04 22:27 ` Brendan Higgins
2019-10-04 22:27 ` Brendan Higgins
2019-10-04 22:27 ` Brendan Higgins
2019-10-04 22:27 ` Brendan Higgins
2019-10-04 22:27 ` Brendan Higgins
2019-10-04 22:47 ` shuah
2019-10-04 22:47 ` shuah
2019-10-04 22:47 ` shuah
2019-10-04 22:47 ` shuah
2019-10-04 22:47 ` shuah
2019-10-04 23:10 ` Brendan Higgins
2019-10-04 23:10 ` Brendan Higgins
2019-10-04 23:10 ` Brendan Higgins
2019-10-04 23:10 ` Brendan Higgins
2019-10-04 23:10 ` Brendan Higgins
2019-10-04 23:15 ` shuah
2019-10-04 23:15 ` shuah
2019-10-04 23:15 ` shuah
2019-10-04 23:15 ` shuah
2019-10-04 23:15 ` shuah
2019-10-04 23:29 ` Theodore Y. Ts'o
2019-10-04 23:29 ` Theodore Y. Ts'o
2019-10-04 23:29 ` Theodore Y. Ts'o
2019-10-04 23:29 ` Theodore Y. Ts'o
2019-10-04 23:29 ` Theodore Y. Ts'o
2019-10-04 23:52 ` Brendan Higgins
2019-10-04 23:52 ` Brendan Higgins
2019-10-04 23:52 ` Brendan Higgins
2019-10-04 23:52 ` Brendan Higgins
2019-10-04 23:52 ` Brendan Higgins
2019-10-04 23:57 ` shuah
2019-10-04 23:57 ` shuah
2019-10-04 23:57 ` shuah
2019-10-04 23:57 ` shuah
2019-10-04 23:57 ` shuah
2019-10-05 0:33 ` Brendan Higgins
2019-10-05 0:33 ` Brendan Higgins
2019-10-05 0:33 ` Brendan Higgins
2019-10-05 0:33 ` Brendan Higgins
2019-10-05 0:33 ` Brendan Higgins
2019-10-05 0:49 ` shuah
2019-10-05 0:49 ` shuah
2019-10-05 0:49 ` shuah
2019-10-05 0:49 ` shuah
2019-10-05 0:49 ` shuah
2019-10-05 1:18 ` Brendan Higgins
2019-10-05 1:18 ` Brendan Higgins
2019-10-05 1:18 ` Brendan Higgins
2019-10-05 1:18 ` Brendan Higgins
2019-10-05 1:18 ` Brendan Higgins
2019-10-06 16:54 ` Theodore Y. Ts'o
2019-10-06 16:54 ` Theodore Y. Ts'o
2019-10-06 16:54 ` Theodore Y. Ts'o
2019-10-06 16:54 ` Theodore Y. Ts'o
2019-10-06 16:54 ` Theodore Y. Ts'o
2019-10-06 17:18 ` Linus Torvalds
2019-10-06 17:18 ` Linus Torvalds
2019-10-06 17:18 ` Linus Torvalds
2019-10-06 17:18 ` Linus Torvalds
2019-10-06 17:18 ` Linus Torvalds
2019-10-07 8:40 ` Brendan Higgins
2019-10-07 8:40 ` Brendan Higgins
2019-10-07 8:40 ` Brendan Higgins
2019-10-07 8:40 ` Brendan Higgins
2019-10-07 8:40 ` Brendan Higgins
2019-10-07 14:42 ` shuah
2019-10-07 14:42 ` shuah
2019-10-07 14:42 ` shuah
2019-10-07 14:42 ` shuah
2019-10-07 14:42 ` shuah
2019-10-07 14:40 ` Steven Rostedt [this message]
2019-10-07 14:40 ` Steven Rostedt
2019-10-07 14:40 ` Steven Rostedt
2019-10-07 14:40 ` Steven Rostedt
2019-10-07 14:40 ` Steven Rostedt
2019-10-07 14:57 ` shuah
2019-10-07 14:57 ` shuah
2019-10-07 14:57 ` shuah
2019-10-07 14:57 ` shuah
2019-10-07 14:57 ` shuah
2019-10-07 8:20 ` Brendan Higgins
2019-10-07 8:20 ` Brendan Higgins
2019-10-07 8:20 ` Brendan Higgins
2019-10-07 8:20 ` Brendan Higgins
2019-10-07 8:20 ` Brendan Higgins
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=20191007104048.66ae7e59@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=Alexander.Levin@microsoft.com \
--cc=Tim.Bird@sony.com \
--cc=amir73il@gmail.com \
--cc=brendanhiggins@google.com \
--cc=dan.carpenter@oracle.com \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=frowand.list@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jdike@addtoit.com \
--cc=joel@jms.id.au \
--cc=jpoimboe@redhat.com \
--cc=julia.lawall@lip6.fr \
--cc=keescook@google.com \
--cc=khilman@baylibre.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=knut.omang@oracle.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=linux-um@lists.infradead.org \
--cc=mcgrof@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=rdunlap@infradead.org \
--cc=richard@nod.at \
--cc=rientjes@google.com \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=shuah@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=wfg@linux.intel.com \
--cc=yamada.masahiro@socionext.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.