linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zhang Huan <zhhuan@gmail.com>
To: "Ted Ts'o" <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: potential memory leak on transaction commit
Date: Tue, 5 Apr 2011 20:35:35 +0800	[thread overview]
Message-ID: <BANLkTin6PyfO+z7+ospeiPYrLnBOce3E2g@mail.gmail.com> (raw)
In-Reply-To: <20110404221009.GD2832@thunk.org>

On Tue, Apr 5, 2011 at 06:10, Ted Ts'o <tytso@mit.edu> wrote:
>
> If you could send me an acknowledgement that it would be OK to add a
>
> Signed-off-by: Zhang Huan <zhhuan@gmail.com>
>
> line to your patch, it would be much appreciated.
>

Yes. please go ahead.

Zhang Huan

  reply	other threads:[~2011-04-05 12:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-08 11:40 potential memory leak on transaction commit Zhang Huan
2011-03-08 13:16 ` Lukas Czerner
2011-03-08 14:43   ` Zhang Huan
2011-03-08 16:13     ` Lukas Czerner
2011-03-15  6:39 ` Zhang Huan
2011-04-04 22:10   ` Ted Ts'o
2011-04-05 12:35     ` Zhang Huan [this message]
2011-04-05 23:27       ` Ted Ts'o

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=BANLkTin6PyfO+z7+ospeiPYrLnBOce3E2g@mail.gmail.com \
    --to=zhhuan@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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;
as well as URLs for NNTP newsgroup(s).