From: Saravana Kannan <saravanak@google.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Saravana Kannan <saravanak@google.com>
Cc: Xu Yang <xu.yang_2@nxp.com>,
kernel-team@android.com, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/3] fw_devlink overlapping cycles fix
Date: Fri, 2 Feb 2024 01:56:32 -0800 [thread overview]
Message-ID: <20240202095636.868578-1-saravanak@google.com> (raw)
This is mainly a bug fix with a additional logging improvement. Lots of
details in Patch 2/3.
Greg,
Can you please pull these into 6.8-rcX after Xu gives the Tested-by?
Xu,
Can you please test this whole series and give your Tested-by if it
fixes your issue? Also, from now on, to debug cycles you just need to
search for debug level logs with "cycle:" in the message and convert
them all to info level logs.
v1 -> v2:
Patch 3: Tweaked the log messages and the commit text.
Saravana Kannan (3):
driver core: Fix device_link_flag_is_sync_state_only()
driver core: fw_devlink: Improve detection of overlapping cycles
driver core: fw_devlink: Improve logs for cycle detection
drivers/base/core.c | 26 ++++++++++++++++++++------
1 file changed, 20 insertions(+), 6 deletions(-)
--
2.43.0.594.gd9cf4e227d-goog
next reply other threads:[~2024-02-02 9:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 9:56 Saravana Kannan [this message]
2024-02-02 9:56 ` [PATCH v2 1/3] driver core: Fix device_link_flag_is_sync_state_only() Saravana Kannan
2024-02-02 9:56 ` [PATCH v2 2/3] driver core: fw_devlink: Improve detection of overlapping cycles Saravana Kannan
2024-02-19 10:59 ` Geert Uytterhoeven
2024-02-20 6:55 ` Saravana Kannan
2024-02-02 9:56 ` [PATCH v2 3/3] driver core: fw_devlink: Improve logs for cycle detection Saravana Kannan
2024-02-02 10:56 ` [EXT] [PATCH v2 0/3] fw_devlink overlapping cycles fix Xu Yang
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=20240202095636.868578-1-saravanak@google.com \
--to=saravanak@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=xu.yang_2@nxp.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 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®