From: Al Viro <viro@ftp.linux.org.uk>
To: Sripathi Kodi <sripathik@in.ibm.com>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
Ingo Molnar <mingo@elte.hu>, Roland McGrath <roland@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [Fwd: Re: [PATCH 2.6.13.1] Patch for invisible threads]
Date: Wed, 21 Sep 2005 04:56:15 +0100 [thread overview]
Message-ID: <20050921035615.GZ7992@ftp.linux.org.uk> (raw)
In-Reply-To: <432F4914.3080905@in.ibm.com>
On Mon, Sep 19, 2005 at 06:26:12PM -0500, Sripathi Kodi wrote:
> Al,
>
> >>Al,
> >>Done. Please find the patch below. I retained proc_task_root_link, because
> >>it has significant amount of code in it.
>
>
> What do you feel about this patch now? Is it good enough to go into the
> kernel?
ACK
prev parent reply other threads:[~2005-09-21 3:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-19 23:26 [Fwd: Re: [PATCH 2.6.13.1] Patch for invisible threads] Sripathi Kodi
2005-09-21 3:56 ` Al Viro [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=20050921035615.GZ7992@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=roland@redhat.com \
--cc=sripathik@in.ibm.com \
--cc=torvalds@osdl.org \
--cc=viro@ZenIV.linux.org.uk \
/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