public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Liu Ying <victor.liu@nxp•com>
To: linux-kernel@vger•kernel.org, dri-devel@lists•freedesktop.org
Cc: linux-next@vger•kernel.org, sfr@canb•auug.org.au,
	gregkh@linuxfoundation•org, rafael@kernel•org,
	andrzej.hajda@intel•com, neil.armstrong@linaro•org,
	rfoss@kernel•org, Laurent.pinchart@ideasonboard•com,
	jonas@kwiboo•se, jernej.skrabec@gmail•com,
	maarten.lankhorst@linux•intel.com, mripard@kernel•org,
	tzimmermann@suse•de, airlied@gmail•com, daniel@ffwll•ch,
	angelogioacchino.delregno@collabora•com, ulf.hansson@linaro•org,
	linus.walleij@linaro•org
Subject: [PATCH v2 1/2] driver core: Export device_is_dependent() to modules
Date: Mon, 27 Nov 2023 13:14:13 +0800	[thread overview]
Message-ID: <20231127051414.3783108-2-victor.liu@nxp.com> (raw)
In-Reply-To: <20231127051414.3783108-1-victor.liu@nxp.com>

Export device_is_dependent() since the drm_kms_helper module is starting
to use it.

Signed-off-by: Liu Ying <victor.liu@nxp•com>
---
v2:
* Newly introduced as needed by patch 2.

 drivers/base/core.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/base/core.c b/drivers/base/core.c
index 67ba592afc77..bfd2bf0364b7 100644
--- a/drivers/base/core.c
+++ b/drivers/base/core.c
@@ -328,6 +328,7 @@ int device_is_dependent(struct device *dev, void *target)
 	}
 	return ret;
 }
+EXPORT_SYMBOL_GPL(device_is_dependent);
 
 static void device_link_init_status(struct device_link *link,
 				    struct device *consumer,
-- 
2.37.1


  reply	other threads:[~2023-11-27  5:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-27  5:14 [PATCH v2 0/2] drm/bridge: panel: Check device dependency before managing device link Liu Ying
2023-11-27  5:14 ` Liu Ying [this message]
2023-11-27 16:38   ` [PATCH v2 1/2] driver core: Export device_is_dependent() to modules Maxime Ripard
2023-11-27 18:20     ` Greg KH
2023-11-27 22:34       ` Linus Walleij
2025-11-26 13:13       ` Bartosz Golaszewski
2025-11-27  8:29         ` Greg KH
2025-11-27 13:19           ` Bartosz Golaszewski
2025-12-03 15:47             ` Greg KH
2025-12-04 10:14               ` Bartosz Golaszewski
2023-11-27  5:14 ` [PATCH v2 2/2] drm/bridge: panel: Check device dependency before managing device link Liu Ying
2023-11-27 16:03 ` [PATCH v2 0/2] " Linus Walleij
2023-11-27 16:29   ` Maxime Ripard
2023-11-27 22:13     ` Linus Walleij
2023-11-29 12:32       ` Maxime Ripard
2023-11-29 14:38         ` Linus Walleij
2023-11-30 10:05           ` Maxime Ripard

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=20231127051414.3783108-2-victor.liu@nxp.com \
    --to=victor.liu@nxp$(echo .)com \
    --cc=Laurent.pinchart@ideasonboard$(echo .)com \
    --cc=airlied@gmail$(echo .)com \
    --cc=andrzej.hajda@intel$(echo .)com \
    --cc=angelogioacchino.delregno@collabora$(echo .)com \
    --cc=daniel@ffwll$(echo .)ch \
    --cc=dri-devel@lists$(echo .)freedesktop.org \
    --cc=gregkh@linuxfoundation$(echo .)org \
    --cc=jernej.skrabec@gmail$(echo .)com \
    --cc=jonas@kwiboo$(echo .)se \
    --cc=linus.walleij@linaro$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=maarten.lankhorst@linux$(echo .)intel.com \
    --cc=mripard@kernel$(echo .)org \
    --cc=neil.armstrong@linaro$(echo .)org \
    --cc=rafael@kernel$(echo .)org \
    --cc=rfoss@kernel$(echo .)org \
    --cc=sfr@canb$(echo .)auug.org.au \
    --cc=tzimmermann@suse$(echo .)de \
    --cc=ulf.hansson@linaro$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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