From: Oleg Nesterov <oleg@redhat.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
Andrew Morton <akpm@linux-foundation.org>,
Arjan van de Ven <arjan@linux.intel.com>,
Tejun Heo <tj@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: + kmod-avoid-deadlock-by-recursive-kmod-call.patch added to -mm tree
Date: Mon, 30 Jan 2012 13:38:19 +0100 [thread overview]
Message-ID: <20120130123819.GA11414@redhat.com> (raw)
In-Reply-To: <87aa56qedn.fsf@rustcorp.com.au>
On 01/30, Rusty Russell wrote:
>
> On Sun, 29 Jan 2012 17:31:41 +0100, Oleg Nesterov <oleg@redhat.com> wrote:
> > Confused... in this case I do not understand why do you dislike the
> > idea to kill khelper_wq.
>
> Yes, you are confused. I was agreeing with you:
Ah...
> I thought "I'd prefer that" was pretty clear??
It was! Looking back, I do not understand how did I manage to misread
your email.
Thanks Rusty,
Oleg.
next prev parent reply other threads:[~2012-01-30 12:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 17:56 + kmod-avoid-deadlock-by-recursive-kmod-call.patch added to -mm tree Oleg Nesterov
2012-01-27 2:55 ` Rusty Russell
2012-01-27 14:32 ` Oleg Nesterov
2012-01-29 0:49 ` Rusty Russell
2012-01-29 16:31 ` Oleg Nesterov
2012-01-29 23:26 ` Rusty Russell
2012-01-30 0:25 ` Tejun Heo
2012-01-30 13:03 ` Oleg Nesterov
2012-01-30 17:28 ` Tejun Heo
2012-02-03 18:00 ` Oleg Nesterov
2012-02-03 19:26 ` Tejun Heo
2012-02-04 12:56 ` + kmod-avoid-deadlock-by-recursive-kmod-call.patch added to-mm tree Tetsuo Handa
2012-02-06 17:19 ` Oleg Nesterov
2012-01-30 12:38 ` Oleg Nesterov [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-01-26 0:41 + kmod-avoid-deadlock-by-recursive-kmod-call.patch added to -mm tree akpm
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=20120130123819.GA11414@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=rusty@rustcorp.com.au \
--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.