From: Tejun Heo <tj@kernel.org>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Yijing Wang <wangyijing@huawei.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Daniel J Blueman <daniel@quora.org>,
Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>,
Yinghai Lu <yinghai@kernel.org>, Jiang Liu <liuj97@gmail.com>
Subject: Re: [PATCH v7 2/4] PCI: shpchp: Make shpchp_wq non-ordered
Date: Mon, 14 Jan 2013 08:49:42 -0800 [thread overview]
Message-ID: <20130114164942.GA27942@mtj.dyndns.org> (raw)
In-Reply-To: <20130113232743.7225.11180.stgit@bhelgaas.mtv.corp.google.com>
Hello,
On Sun, Jan 13, 2013 at 04:27:43PM -0700, Bjorn Helgaas wrote:
> e24dcbef93 ("shpchp: update workqueue usage") was described as adding
> non-ordered shpchp_wq, but it actually made it an *ordered* workqueue.
>
> This patch changes shpchp_wq to be non-ordered, as described in the
> e24dcbef93 commit log and as was done for pciehp by a827ea307b ("pciehp:
> update workqueue usage").
>
> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
> CC: Tejun Heo <tj@kernel.org>
Yeap, my mistake.
Acked-by: Tejun Heo <tj@kernel.org>
Thanks!
--
tejun
next prev parent reply other threads:[~2013-01-14 16:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-13 23:27 [PATCH v7 0/4] PCI: pciehp, shpchp deadlock fixes Bjorn Helgaas
2013-01-13 23:27 ` [PATCH v7 1/4] PCI: pciehp: Use per-slot workqueues to avoid deadlock Bjorn Helgaas
2013-01-13 23:27 ` [PATCH v7 2/4] PCI: shpchp: Make shpchp_wq non-ordered Bjorn Helgaas
2013-01-14 16:49 ` Tejun Heo [this message]
2013-01-13 23:27 ` [PATCH v7 3/4] PCI: shpchp: Handle push button event asynchronously Bjorn Helgaas
2013-01-13 23:27 ` [PATCH v7 4/4] PCI: shpchp: Use per-slot workqueues to avoid deadlock Bjorn Helgaas
2013-01-14 1:30 ` [PATCH v7 0/4] PCI: pciehp, shpchp deadlock fixes Yijing Wang
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=20130114164942.GA27942@mtj.dyndns.org \
--to=tj@kernel.org \
--cc=bhelgaas@google.com \
--cc=daniel@quora.org \
--cc=kaneshige.kenji@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=liuj97@gmail.com \
--cc=wangyijing@huawei.com \
--cc=yinghai@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).