All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: Lai Jiangshan <laijs@cn.fujitsu.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH v3 wq/for-3.19 3/3] workqueue: dump workqueues on sysrq-t
Date: Tue, 10 Mar 2015 08:58:42 -0400	[thread overview]
Message-ID: <20150310125842.GC28730@htj.duckdns.org> (raw)
In-Reply-To: <20150309132828.GT13283@htj.duckdns.org>

On Mon, Mar 09, 2015 at 09:28:28AM -0400, Tejun Heo wrote:
> Now that %pb[l] formatting is now in mainline, this can go forward.
> Here's the updated patch which uses printf instead of the fixed buffer
> when printing cpus.  I couldn't find a better option at the moment and
> am still appending the output to sysrq-t.  This only prints out the
> workqueues and pools with busy work items so the amount of extra
> output should be fairly low in general.  If nobody objects, I'll route
> these through wq/for-4.1.

Applied to wq/for-4.1.

Thanks.

-- 
tejun

      reply	other threads:[~2015-03-10 12:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-08 17:43 [PATCH wq/for-3.19 1/3] workqueue: make the workqueues list RCU walkable Tejun Heo
2014-12-08 17:44 ` [PATCH wq/for-3.19 2/3] workqueue: keep track of the flushing task and pool manager Tejun Heo
2014-12-08 17:47   ` [PATCH wq/for-3.19 3/3] workqueue: dump workqueues on sysrq-t Tejun Heo
2014-12-08 18:06     ` Andrew Morton
2014-12-08 18:40       ` Tejun Heo
2014-12-08 19:05         ` Andrew Morton
2014-12-08 19:22           ` Tejun Heo
2014-12-10  4:50             ` Greg Kroah-Hartman
2014-12-10 18:34               ` Tejun Heo
2015-03-09 13:28     ` [PATCH v3 " Tejun Heo
2015-03-10 12:58       ` Tejun Heo [this message]

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=20150310125842.GC28730@htj.duckdns.org \
    --to=tj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=torvalds@linux-foundation.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.