From: Namhyung Kim <namhyung@gmail.com>
To: Tejun Heo <tj@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] workqueue: mark lock acquisition on worker_maybe_bind_and_lock()
Date: Tue, 24 Aug 2010 00:01:01 +0900 [thread overview]
Message-ID: <1282575661.1659.6.camel@leonhard> (raw)
In-Reply-To: <4C72423E.3000402@kernel.org>
2010-08-23 (월), 11:41 +0200, Tejun Heo:
> Also, please considering putting related patches into a thread. For
> short series, just chaining them is good enough (ie. patch n+1 is
> reply to patch n). For longer series, writing up a head message with
> overall description, diffstat and other general info about the patch
> series and making all patches reaplies to the head message is a good
> idea.
>
> Thanks.
>
OK. I see. Thank you for the advice.
--
Regards,
Namhyung Kim
prev parent reply other threads:[~2010-08-23 15:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-22 14:19 [PATCH 2/2] workqueue: mark lock acquisition on worker_maybe_bind_and_lock() Namhyung Kim
2010-08-23 9:41 ` Tejun Heo
2010-08-23 15:01 ` Namhyung Kim [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=1282575661.1659.6.camel@leonhard \
--to=namhyung@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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 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.