From: Matthias Kaehlcke <mka@chromium.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Alan Stern <stern@rowland.harvard.edu>,
Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Mathias Nyman <mathias.nyman@intel.com>,
Felipe Balbi <balbi@kernel.org>
Cc: Bastien Nocera <hadess@hadess.net>,
Krzysztof Kozlowski <krzk@kernel.org>,
Douglas Anderson <dianders@chromium.org>,
Peter Chen <peter.chen@kernel.org>,
Ravi Chandra Sadineni <ravisadineni@chromium.org>,
linux-usb@vger.kernel.org, Roger Quadros <rogerq@kernel.org>,
Michal Simek <michal.simek@xilinx.com>,
linux-kernel@vger.kernel.org, Stephen Boyd <swboyd@chromium.org>,
devicetree@vger.kernel.org, Matthias Kaehlcke <mka@chromium.org>,
"Rafael J. Wysocki" <rafael@kernel.org>
Subject: [PATCH v19 2/5] driver core: Export device_is_bound()
Date: Wed, 12 Jan 2022 11:10:45 -0800 [thread overview]
Message-ID: <20220112111028.v19.2.Ie1de382686d61909e17fa8def2b83899256e8f5d@changeid> (raw)
In-Reply-To: <20220112191048.837236-1-mka@chromium.org>
Export device_is_bound() to enable its use by drivers that are
built as modules.
Signed-off-by: Matthias Kaehlcke <mka@chromium.org>
---
Changes in v19:
- none
Changes in v18:
- patch added to the series
drivers/base/dd.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/base/dd.c b/drivers/base/dd.c
index 68ea1f949daa..07eefddd4a77 100644
--- a/drivers/base/dd.c
+++ b/drivers/base/dd.c
@@ -370,6 +370,7 @@ bool device_is_bound(struct device *dev)
{
return dev->p && klist_node_attached(&dev->p->knode_driver);
}
+EXPORT_SYMBOL_GPL(device_is_bound);
static void driver_bound(struct device *dev)
{
--
2.34.1.575.g55b058a8bb-goog
next prev parent reply other threads:[~2022-01-12 19:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 19:10 [PATCH v19 0/5] usb: misc: Add onboard_usb_hub driver Matthias Kaehlcke
2022-01-12 19:10 ` [PATCH v19 1/5] of/platform: Add stubs for of_platform_device_create/destroy() Matthias Kaehlcke
2022-01-12 22:01 ` Stephen Boyd
2022-01-13 1:02 ` Doug Anderson
2022-01-12 19:10 ` Matthias Kaehlcke [this message]
2022-01-13 1:02 ` [PATCH v19 2/5] driver core: Export device_is_bound() Doug Anderson
2022-01-13 3:49 ` Stephen Boyd
2022-01-12 19:10 ` [PATCH v19 3/5] usb: misc: Add onboard_usb_hub driver Matthias Kaehlcke
2022-01-13 1:02 ` Doug Anderson
2022-01-13 3:49 ` Stephen Boyd
2022-01-13 18:38 ` Matthias Kaehlcke
2022-01-12 19:10 ` [PATCH v19 4/5] usb: core: hcd: Create platform devices for onboard hubs in probe() Matthias Kaehlcke
2022-01-13 1:03 ` Doug Anderson
2022-01-13 3:50 ` Stephen Boyd
2022-01-12 19:10 ` [PATCH v19 5/5] arm64: dts: qcom: sc7180-trogdor: Add nodes for onboard USB hub Matthias Kaehlcke
2022-01-12 20:47 ` Stephen Boyd
2022-01-12 20:51 ` Matthias Kaehlcke
2022-01-12 22:00 ` Stephen Boyd
2022-01-13 1:03 ` Doug Anderson
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=20220112111028.v19.2.Ie1de382686d61909e17fa8def2b83899256e8f5d@changeid \
--to=mka@chromium.org \
--cc=balbi@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=frowand.list@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hadess@hadess.net \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=michal.simek@xilinx.com \
--cc=peter.chen@kernel.org \
--cc=rafael@kernel.org \
--cc=ravisadineni@chromium.org \
--cc=robh+dt@kernel.org \
--cc=rogerq@kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=swboyd@chromium.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 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).