From: Tejun Heo <tj@kernel.org> To: Roger Lu <roger.lu@mediatek.com> Cc: "Rafael J . Wysocki" <rjw@rjwysocki.net>, Len Brown <len.brown@intel.com>, Pavel Machek <pavel@ucw.cz>, srv_heupstream@mediatek.com, linux-mediatek@lists.infradead.org, Sascha Hauer <kernel@pengutronix.de>, Lai Jiangshan <jiangshanlai@gmail.com>, Matthias Brugger <matthias.bgg@gmail.com>, linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH] PM / suspend: show workqueue state in suspend flow Date: Thu, 30 Jun 2016 04:51:03 -0500 [thread overview] Message-ID: <20160630095103.GB28719@htj.duckdns.org> (raw) In-Reply-To: <1467256666-27808-1-git-send-email-roger.lu@mediatek.com> Hello, On Thu, Jun 30, 2016 at 11:17:46AM +0800, Roger Lu wrote: > + if (wq->flags & WQ_FREEZABLE) > + pr_info("freezable "); The flag is already printed below and doing this will make the output more difficult to read. > pr_info("workqueue %s: flags=0x%x\n", wq->name, wq->flags); Thanks. -- tejun
WARNING: multiple messages have this Message-ID (diff)
From: tj@kernel.org (Tejun Heo) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH] PM / suspend: show workqueue state in suspend flow Date: Thu, 30 Jun 2016 04:51:03 -0500 [thread overview] Message-ID: <20160630095103.GB28719@htj.duckdns.org> (raw) In-Reply-To: <1467256666-27808-1-git-send-email-roger.lu@mediatek.com> Hello, On Thu, Jun 30, 2016 at 11:17:46AM +0800, Roger Lu wrote: > + if (wq->flags & WQ_FREEZABLE) > + pr_info("freezable "); The flag is already printed below and doing this will make the output more difficult to read. > pr_info("workqueue %s: flags=0x%x\n", wq->name, wq->flags); Thanks. -- tejun
next prev parent reply other threads:[~2016-06-30 9:51 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-06-30 3:17 [PATCH] PM / suspend: show workqueue state in suspend flow Roger Lu 2016-06-30 3:17 ` Roger Lu 2016-06-30 3:17 ` Roger Lu 2016-06-30 9:51 ` Tejun Heo [this message] 2016-06-30 9:51 ` Tejun Heo
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=20160630095103.GB28719@htj.duckdns.org \ --to=tj@kernel.org \ --cc=jiangshanlai@gmail.com \ --cc=kernel@pengutronix.de \ --cc=len.brown@intel.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mediatek@lists.infradead.org \ --cc=linux-pm@vger.kernel.org \ --cc=matthias.bgg@gmail.com \ --cc=pavel@ucw.cz \ --cc=rjw@rjwysocki.net \ --cc=roger.lu@mediatek.com \ --cc=srv_heupstream@mediatek.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: linkBe 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.