From: Libin <huawei.libin@huawei.com>
To: Tejun Heo <tj@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <guohanjun@huawei.com>,
<wangyijing@huawei.com>
Subject: Re: [PATCH] workqueue: Correct/Drop references to gcwq in Documentation
Date: Tue, 20 Aug 2013 09:35:24 +0800 [thread overview]
Message-ID: <5212C7DC.3060707@huawei.com> (raw)
In-Reply-To: <20130816144730.GC2505@htj.dyndns.org>
On 2013/8/16 22:47, Tejun Heo wrote:
> On Fri, Aug 16, 2013 at 01:33:17PM +0800, Libin wrote:
>> No functional changes. This patch fixes the post gcwq comments in
>> Documentation/workqueue.txt.
>>
>> Signed-off-by: Libin <huawei.libin@huawei.com>
>
> Thanks a lot for doing this. Can you please update the unbound pool
> part accordingly as described in one of the replies? Also, it'd be
> nice if you bundle these three into a single thread so that the
> patches are easier to track.
>
> Thanks!
>
OK, I will update the patchs and post the patch set soon.
Thanks,
Libin
prev parent reply other threads:[~2013-08-20 1:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-16 5:33 [PATCH] workqueue: Correct/Drop references to gcwq in Documentation Libin
2013-08-16 14:47 ` Tejun Heo
2013-08-20 1:35 ` Libin [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=5212C7DC.3060707@huawei.com \
--to=huawei.libin@huawei.com \
--cc=guohanjun@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
--cc=wangyijing@huawei.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 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.