Thread (55 messages) 55 messages, 3 authors, 2019-08-12

Re: [PATCH v9 02/18] kunit: test: add test resource management API

From: Stephen Boyd <sboyd@kernel.org>
Date: 2019-07-15 20:51:07
Also in: dri-devel, linux-doc, linux-fsdevel, linux-kbuild, linux-kselftest, linux-um, lkml, nvdimm

Quoting Brendan Higgins (2019-07-15 13:30:22)
On Mon, Jul 15, 2019 at 1:24 PM Stephen Boyd [off-list ref] wrote:
quoted
Quoting Brendan Higgins (2019-07-12 01:17:28)
quoted
diff --git a/kunit/test.c b/kunit/test.c
index 571e4c65deb5c..f165c9d8e10b0 100644
quoted
One solution would be to piggyback on all the existing devres allocation
logic we already have and make each struct kunit a device that we pass
into the devres functions. A far simpler solution would be to just
copy/paste what devres does and use a spinlock and an allocation
function that takes GFP flags.
Yeah, that's what I did originally, but I thought from the discussion
on patch 01 that you thought a spinlock was overkill for struct kunit.
I take it you only meant in that initial patch?
Correct. I was only talking about the success bit in there.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help