mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrzej Hajda <a.hajda@samsung.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>
Cc: Andrzej Hajda <a.hajda@samsung.com>,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	linux-kernel@vger.kernel.org,
	Russell King - ARM Linux <linux@armlinux.org.uk>
Subject: [PATCH] component: do not stop components lookup after first fail
Date: Thu, 06 Dec 2018 15:11:47 +0100	[thread overview]
Message-ID: <20181206141147.15375-1-a.hajda@samsung.com> (raw)
In-Reply-To: <CGME20181206141159eucas1p2d8855194db968d33f30a82f0fe1ae638@eucas1p2.samsung.com>

Currently showing content of /sys/kernel/debug/device_component/*
works partially, in case one of the components is not available this and
all remaining components have status not-registered, but the problem
is only with the first one.
Allowing to finish lookup for other components in case one is missing
solves the issue.

Signed-off-by: Andrzej Hajda <a.hajda@samsung.com>
---
 drivers/base/component.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/base/component.c b/drivers/base/component.c
index e8d676fad0c9..e9572b37d5cf 100644
--- a/drivers/base/component.c
+++ b/drivers/base/component.c
@@ -179,7 +179,7 @@ static int find_components(struct master *master)
 		c = find_component(master, mc->compare, mc->data);
 		if (!c) {
 			ret = -ENXIO;
-			break;
+			continue;
 		}
 
 		dev_dbg(master->dev, "found component %s, duplicate %u\n", dev_name(c->dev), !!c->master);
-- 
2.17.1


           reply	other threads:[~2018-12-06 14:12 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CGME20181206141159eucas1p2d8855194db968d33f30a82f0fe1ae638@eucas1p2.samsung.com>]

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=20181206141147.15375-1-a.hajda@samsung.com \
    --to=a.hajda@samsung.com \
    --cc=b.zolnierkie@samsung.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=m.szyprowski@samsung.com \
    --cc=rafael@kernel.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

all inboxes | Powered by JetHome®