All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <swboyd@chromium.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, Saravana Kannan <saravanak@google.com>
Subject: [PATCH] driver core: Make dev_info() messages dev_dbg()
Date: Wed,  2 Jun 2021 23:48:49 -0700	[thread overview]
Message-ID: <20210603064849.1376107-1-swboyd@chromium.org> (raw)

These seem to mostly print debug information about device link stuff at
boot. They don't seem very useful outside of debugging so move them to
dev_dbg().

Cc: Saravana Kannan <saravanak@google.com>
Signed-off-by: Stephen Boyd <swboyd@chromium.org>
---
 drivers/base/core.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/base/core.c b/drivers/base/core.c
index 628e33939aca..066880a843bc 100644
--- a/drivers/base/core.c
+++ b/drivers/base/core.c
@@ -865,7 +865,7 @@ static void __device_link_del(struct kref *kref)
 {
 	struct device_link *link = container_of(kref, struct device_link, kref);
 
-	dev_info(link->consumer, "Dropping the link to %s\n",
+	dev_dbg(link->consumer, "Dropping the link to %s\n",
 		 dev_name(link->supplier));
 
 	pm_runtime_drop_link(link);
@@ -1732,7 +1732,7 @@ static int fw_devlink_create_devlink(struct device *con,
 		 */
 		if (!device_link_add(con, sup_dev, flags) &&
 		    !(flags & DL_FLAG_SYNC_STATE_ONLY)) {
-			dev_info(con, "Fixing up cyclic dependency with %s\n",
+			dev_dbg(con, "Fixing up cyclic dependency with %s\n",
 				 dev_name(sup_dev));
 			device_links_write_lock();
 			fw_devlink_relax_cycle(con, sup_dev);

base-commit: 5fcd0bc17e451e8f140067131fd12be0f5f1204c
-- 
https://chromeos.dev


             reply	other threads:[~2021-06-03  6:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-03  6:48 Stephen Boyd [this message]
2021-06-03 16:18 ` [PATCH] driver core: Make dev_info() messages dev_dbg() Saravana Kannan
2021-06-03 20:17   ` Stephen Boyd

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=20210603064849.1376107-1-swboyd@chromium.org \
    --to=swboyd@chromium.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=saravanak@google.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.