Commit 6c0d57b4 authored by Viresh Kumar's avatar Viresh Kumar Committed by Johan Hovold

greybus: connection: protocol can be NULL in gb_connection_exit()

gb_connection_exit() is getting called from gb_connection_destroy() now,
which will get called from failure path of gb_connection_create_range()
(in a later commit). And at that point connection->protocol will be
NULL.

Don't print an error message if this happens in gb_connection_exit().
Signed-off-by: default avatarViresh Kumar <viresh.kumar@linaro.org>
Signed-off-by: default avatarJohan Hovold <johan@hovoldconsulting.com>
parent 50bb9cca
...@@ -396,10 +396,8 @@ static int gb_connection_init(struct gb_connection *connection) ...@@ -396,10 +396,8 @@ static int gb_connection_init(struct gb_connection *connection)
static void gb_connection_exit(struct gb_connection *connection) static void gb_connection_exit(struct gb_connection *connection)
{ {
if (!connection->protocol) { if (!connection->protocol)
dev_warn(&connection->dev, "exit without protocol.\n");
return; return;
}
spin_lock_irq(&connection->lock); spin_lock_irq(&connection->lock);
if (connection->state != GB_CONNECTION_STATE_ENABLED) { if (connection->state != GB_CONNECTION_STATE_ENABLED) {
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment