All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saravana Kannan <saravanak@google.com>
To: Stephen Boyd <swboyd@chromium.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] driver core: Make cycle dev_info() message dev_dbg()
Date: Thu, 3 Jun 2021 15:27:37 -0700	[thread overview]
Message-ID: <CAGETcx_G9iXgvRupZdeteHSwhAFZNYNn1ti4bGL8F0dQeDWhEg@mail.gmail.com> (raw)
In-Reply-To: <20210603202116.1841261-1-swboyd@chromium.org>

On Thu, Jun 3, 2021 at 1:21 PM Stephen Boyd <swboyd@chromium.org> wrote:
>
> This seems to mostly print debug information about device link stuff at
> boot. It doesn't seem very useful outside of debugging so move it to
> dev_dbg().

As before, Nak at least for now.

This code path really shouldn't be exercised on most systems. I might
be open to this once fw_delink bug reports stop coming in for at least
1 full kernel minor version.

-Saravana


>
> Cc: Saravana Kannan <saravanak@google.com>
> Signed-off-by: Stephen Boyd <swboyd@chromium.org>
> ---
>
> Changes from v1 (https://lore.kernel.org/r/20210603064849.1376107-1-swboyd@chromium.org)
>  * Dropped second hunk and rebased to -rc4
>
>  drivers/base/core.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/base/core.c b/drivers/base/core.c
> index 54ba506e5a89..378bb894869a 100644
> --- a/drivers/base/core.c
> +++ b/drivers/base/core.c
> @@ -1736,7 +1736,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: 8124c8a6b35386f73523d27eacb71b5364a68c4c
> --
> https://chromeos.dev
>

  reply	other threads:[~2021-06-03 22:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-03 20:21 [PATCH v2] driver core: Make cycle dev_info() message dev_dbg() Stephen Boyd
2021-06-03 22:27 ` Saravana Kannan [this message]
2021-06-04 13:00 ` Greg Kroah-Hartman
2021-06-04 20:18   ` 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=CAGETcx_G9iXgvRupZdeteHSwhAFZNYNn1ti4bGL8F0dQeDWhEg@mail.gmail.com \
    --to=saravanak@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.