From: Tejun Heo <tj@kernel.org>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: linux-pci@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2.6.36-rc7 2/2] shpchp: update workqueue usage
Date: Mon, 18 Oct 2010 08:34:09 +0200 [thread overview]
Message-ID: <4CBBEA61.5000507@kernel.org> (raw)
In-Reply-To: <4CBBD4F6.2080506@kernel.org>
On 10/18/2010 07:02 AM, Tejun Heo wrote:
> Hello,
>
> On 10/18/2010 05:03 AM, Jesse Barnes wrote:
>> ...and dropped again. Hadn't realized they depend on stuff from your
>> workqueue tree. Please just include them there assuming Kenji-san
>> doesn't nack them.
>>
>> Acked-by: Jesse Barnes <jbarnes@virtuousgeek.org>
>
> Ah, sorry about that. I for some reason thought alloc_ordered_queue()
> was already mainline. I'll route this through the wq tree.
Both patches applied to wq#for-next. Thank you.
--
tejun
prev parent reply other threads:[~2010-10-18 6:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-15 14:47 [PATCH v2.6.36-rc7 1/2] pciehp: " Tejun Heo
2010-10-15 14:47 ` [PATCH v2.6.36-rc7 2/2] shpchp: " Tejun Heo
2010-10-15 19:52 ` Jesse Barnes
2010-10-15 20:08 ` Tejun Heo
2010-10-15 20:17 ` Jesse Barnes
2010-10-15 21:25 ` Kenji Kaneshige
2010-10-18 3:03 ` Jesse Barnes
2010-10-18 5:02 ` Tejun Heo
2010-10-18 6:34 ` 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=4CBBEA61.5000507@kernel.org \
--to=tj@kernel.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.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
Powered by JetHome