mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Jungseung Lee <js07.lee@samsung.com>
Cc: Lai Jiangshan <jiangshanlai@gmail.com>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Pavel Machek <pavel@ucw.cz>, Len Brown <len.brown@intel.com>,
	linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
	bw365.lee@samsung.com, yw85.kim@samsung.com,
	huijin.park@samsung.com
Subject: Re: [PATCH] workqueue: Introduce show_freeze_workqueues_busy
Date: Fri, 17 Mar 2023 12:16:22 -1000	[thread overview]
Message-ID: <ZBTmtiyHpreu2btd@slm.duckdns.org> (raw)
In-Reply-To: <1678884357-38253-1-git-send-email-js07.lee@samsung.com>

Hello,

A few nits.

On Wed, Mar 15, 2023 at 09:45:57PM +0900, Jungseung Lee wrote:
> diff --git a/kernel/power/process.c b/kernel/power/process.c
> index 6c1c7e5..590550f 100644
> --- a/kernel/power/process.c
> +++ b/kernel/power/process.c
> @@ -93,7 +93,7 @@ static int try_to_freeze_tasks(bool user_only)
>  		       todo - wq_busy, wq_busy);
>  
>  		if (wq_busy)
> -			show_all_workqueues();
> +			show_freeze_workqueues_busy();

Maybe name this show_freezable_workqueues()?

> @@ -5043,7 +5043,7 @@ static void show_one_worker_pool(struct worker_pool *pool)
>  /**
>   * show_all_workqueues - dump workqueue state
>   *
> - * Called from a sysrq handler or try_to_freeze_tasks() and prints out
> + * Called from a sysrq handler and prints out
>   * all busy workqueues and pools.

Can you reflow the comment to 80-col?

> +/**
> + * show_freeze_workqueues_busy - dump freezable workqueue state
> + *
> + * Called from try_to_freeze_tasks() and prints out
> + * all freezable workqueues still busy.

Ditto.

Thanks.

-- 
tejun

  reply	other threads:[~2023-03-17 22:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20230315130515epcas1p40823f20da586c1b5813b41e66e754309@epcas1p4.samsung.com>
2023-03-15 12:45 ` Jungseung Lee
2023-03-17 22:16   ` Tejun Heo [this message]
2023-03-20  2:55     ` Jungseung Lee

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=ZBTmtiyHpreu2btd@slm.duckdns.org \
    --to=tj@kernel.org \
    --cc=bw365.lee@samsung.com \
    --cc=huijin.park@samsung.com \
    --cc=jiangshanlai@gmail.com \
    --cc=js07.lee@samsung.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=rafael@kernel.org \
    --cc=yw85.kim@samsung.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®