oe-kbuild-all.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Maxime Ripard <mripard@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev,
	"Linux Memory Management List" <linux-mm@kvack.org>,
	"Javier Martinez Canillas" <javierm@redhat.com>,
	"Maíra Canal" <mairacanal@riseup.net>
Subject: [linux-next:master 5284/8441] drivers/gpu/drm/tests/drm_kunit_helpers.c:171: warning: expecting prototype for drm_kunit_helper_context_alloc(). Prototype was for drm_kunit_helper_acquire_ctx_alloc() instead
Date: Fri, 11 Aug 2023 23:42:30 +0800	[thread overview]
Message-ID: <202308112307.TPmYbd3L-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   21ef7b1e17d039053edaeaf41142423810572741
commit: 6e193f9fbbb02e1bde88510a71823e5bf83c2010 [5284/8441] drm/tests: helpers: Create a helper to allocate a locking ctx
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20230811/202308112307.TPmYbd3L-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce: (https://download.01.org/0day-ci/archive/20230811/202308112307.TPmYbd3L-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202308112307.TPmYbd3L-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/gpu/drm/tests/drm_kunit_helpers.c:171: warning: expecting prototype for drm_kunit_helper_context_alloc(). Prototype was for drm_kunit_helper_acquire_ctx_alloc() instead


vim +171 drivers/gpu/drm/tests/drm_kunit_helpers.c

   156	
   157	/**
   158	 * drm_kunit_helper_context_alloc - Allocates an acquire context
   159	 * @test: The test context object
   160	 *
   161	 * Allocates and initializes a modeset acquire context.
   162	 *
   163	 * The context is tied to the kunit test context, so we must not call
   164	 * drm_modeset_acquire_fini() on it, it will be done so automatically.
   165	 *
   166	 * Returns:
   167	 * An ERR_PTR on error, a pointer to the newly allocated context otherwise
   168	 */
   169	struct drm_modeset_acquire_ctx *
   170	drm_kunit_helper_acquire_ctx_alloc(struct kunit *test)
 > 171	{
   172		struct drm_modeset_acquire_ctx *ctx;
   173		int ret;
   174	
   175		ctx = kunit_kzalloc(test, sizeof(*ctx), GFP_KERNEL);
   176		KUNIT_ASSERT_NOT_NULL(test, ctx);
   177	
   178		drm_modeset_acquire_init(ctx, 0);
   179	
   180		ret = kunit_add_action_or_reset(test,
   181						action_drm_release_context,
   182						ctx);
   183		if (ret)
   184			return ERR_PTR(ret);
   185	
   186		return ctx;
   187	}
   188	EXPORT_SYMBOL_GPL(drm_kunit_helper_acquire_ctx_alloc);
   189	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

             reply	other threads:[~2023-08-11 15:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-11 15:42 kernel test robot [this message]
2023-08-11 15:53 [linux-next:master 5284/8441] drivers/gpu/drm/tests/drm_kunit_helpers.c:171: warning: expecting prototype for drm_kunit_helper_context_alloc(). Prototype was for drm_kunit_helper_acquire_ctx_alloc() instead kernel test robot

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=202308112307.TPmYbd3L-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=javierm@redhat.com \
    --cc=linux-mm@kvack.org \
    --cc=mairacanal@riseup.net \
    --cc=mripard@kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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).