All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Norris <briannorris@chromium.org>
To: kernel test robot <lkp@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	devel@driverdev.osuosl.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Maxime Ripard <mripard@kernel.org>,
	David Gow <davidgow@google.com>
Subject: Re: [driver-core:driver-core-testing 29/29] include/kunit/platform_device.h:15:15: warning: declaration of 'struct completion' will not be visible outside of this function
Date: Thu, 2 Jan 2025 10:39:11 -0800	[thread overview]
Message-ID: <Z3bdT0DrjcV6UzHe@google.com> (raw)
In-Reply-To: <202412241917.orLfjA92-lkp@intel.com>

On Tue, Dec 24, 2024 at 07:37:20PM +0800, kernel test robot wrote:
> All warnings (new ones prefixed by >>):
> 
>    In file included from drivers/base/test/platform-device-test.c:3:
> >> include/kunit/platform_device.h:15:15: warning: declaration of 'struct completion' will not be visible outside of this function [-Wvisibility]
>       15 |                                                  struct completion *x);
>          |                                                         ^
>    1 warning generated.

Same:

https://lore.kernel.org/lkml/20241213180841.3023843-1-briannorris@chromium.org/
Subject: [PATCH] kunit: platform: Resolve 'struct completion' warning

Brian


  reply	other threads:[~2025-01-02 18:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-24 11:37 [driver-core:driver-core-testing 29/29] include/kunit/platform_device.h:15:15: warning: declaration of 'struct completion' will not be visible outside of this function kernel test robot
2025-01-02 18:39 ` Brian Norris [this message]
2025-01-03 15:52   ` Greg Kroah-Hartman
2025-01-03 17:49     ` Brian Norris
2025-01-04  8:16       ` Greg Kroah-Hartman

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=Z3bdT0DrjcV6UzHe@google.com \
    --to=briannorris@chromium.org \
    --cc=davidgow@google.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --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 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.