linux-kernel - [PATCH] component: demote bind messages to debug level

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <1445860183-8535-1-git-send-email-l.stach@pengutronix.de>
Date:	Mon, 26 Oct 2015 12:49:43 +0100
From:	Lucas Stach <l.stach@...gutronix.de>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:	Russell King - ARM Linux <linux@....linux.org.uk>,
	linux-kernel@...r.kernel.org, patchwork-lst@...gutronix.de
Subject: [PATCH] component: demote bind messages to debug level

The component bind messages are mostly redundant as most drivers print
a more specific message themselves when binding has succeeded. As they
don't add much value, but can get noisy with a lot of components in the
system demote them to debug level.

Signed-off-by: Lucas Stach <l.stach@...gutronix.de>
---
 drivers/base/component.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/base/component.c b/drivers/base/component.c
index f748430bb654..867ace2404f1 100644
--- a/drivers/base/component.c
+++ b/drivers/base/component.c
@@ -417,8 +417,8 @@ static int component_bind(struct component *component, struct master *master,
 		devres_close_group(component->dev, NULL);
 		devres_remove_group(master->dev, NULL);
 
-		dev_info(master->dev, "bound %s (ops %ps)\n",
-			 dev_name(component->dev), component->ops);
+		dev_dbg(master->dev, "bound %s (ops %ps)\n",
+			dev_name(component->dev), component->ops);
 	} else {
 		devres_release_group(component->dev, NULL);
 		devres_release_group(master->dev, NULL);
-- 
2.6.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/