All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [RFC PATCH] kunit: kunit_release_resource() can be static
Date: Wed, 04 Mar 2020 11:11:25 +0800	[thread overview]
Message-ID: <20200304031049.GA33024@66eee00062b6> (raw)
In-Reply-To: <1583251361-12748-2-git-send-email-alan.maguire@oracle.com>

[-- Attachment #1: Type: text/plain, Size: 710 bytes --]


Fixes: 3309c9afd2cc ("kunit: generalize kunit_resource API beyond allocated resources")
Signed-off-by: kbuild test robot <lkp@intel.com>
---
 test.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/kunit/test.c b/lib/kunit/test.c
index 132e9bf0ccffc..5d6da6b37348f 100644
--- a/lib/kunit/test.c
+++ b/lib/kunit/test.c
@@ -325,7 +325,7 @@ int kunit_run_tests(struct kunit_suite *suite)
 EXPORT_SYMBOL_GPL(kunit_run_tests);
 
 /* Called when refcount reaches zero. */
-void kunit_release_resource(struct kref *kref)
+static void kunit_release_resource(struct kref *kref)
 {
 	struct kunit_resource *res = container_of(kref, struct kunit_resource,
 						  refcount);

  parent reply	other threads:[~2020-03-04  3:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-03 16:02 [RFC PATCH kunit-next 0/2] kunit: extend kunit resources API Alan Maguire
2020-03-03 16:02 ` [RFC PATCH kunit-next 1/2] kunit: generalize kunit_resource API beyond allocated resources Alan Maguire
2020-03-04  3:10   ` kbuild test robot
2020-03-04  3:11   ` kbuild test robot [this message]
2020-03-12  0:14   ` Brendan Higgins
2020-03-03 16:02 ` [RFC PATCH kunit-next 2/2] kunit: add support for named resources Alan Maguire
2020-03-13  0:09   ` 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=20200304031049.GA33024@66eee00062b6 \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.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 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.