From: Theodore Ts'o <tytso@mit.edu>
To: Andreas Dilger <adilger@dilger.ca>
Cc: "vikram.jadhav07" <vikramjadhavpucsd2007@gmail.com>,
linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] ext4: Buffer Head Leak In mmp
Date: Mon, 14 Mar 2016 10:40:03 -0400 [thread overview]
Message-ID: <20160314144002.GN29218@thunk.org> (raw)
In-Reply-To: <BFF88A70-A864-4957-A807-30C6191C4D45@dilger.ca>
On Mon, Mar 14, 2016 at 02:41:34AM -0600, Andreas Dilger wrote:
> On Mar 13, 2016, at 3:57 PM, Theodore Ts'o <tytso@mit.edu> wrote:
> >
> > I've made the changes Andreas suggested, and ended up with this. Andreas, PTAL?
>
> Sorry, not sure what "PTAL" means... :-)
"Please take a look".
> In any case, the patch looks good to me.
Which is sometimes abbreviated "LGTM". :-)
Thanks for the code review!
- Ted
prev parent reply other threads:[~2016-03-14 14:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 15:48 [PATCH] ext4: Buffer Head Leak In mmp vikram.jadhav07
2016-02-08 21:40 ` Andreas Dilger
2016-03-13 21:57 ` Theodore Ts'o
2016-03-14 8:41 ` Andreas Dilger
2016-03-14 14:40 ` Theodore Ts'o [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=20160314144002.GN29218@thunk.org \
--to=tytso@mit.edu \
--cc=adilger@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=vikramjadhavpucsd2007@gmail.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 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).