linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: Dan Carpenter <error27@gmail.com>,
	adilger@sun.com, linux-ext4@vger.kernel.org
Subject: Re: locking typo in ext4_mb_add_n_trim()
Date: Fri, 27 Mar 2009 19:20:45 -0400	[thread overview]
Message-ID: <20090327232045.GH5176@mit.edu> (raw)
In-Reply-To: <20090327163517.GA2810@skywalker>

On Fri, Mar 27, 2009 at 10:05:17PM +0530, Aneesh Kumar K.V wrote:
> 
> Good catch. Can you send a proper patch with signed-off-by. You can add

No need, I've already created a proper patch for this problem, and am
adding it to the ext4 patch queue.

Thanks, Dan!!

						- Ted

      reply	other threads:[~2009-03-27 23:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-27 10:27 locking typo in ext4_mb_add_n_trim() Dan Carpenter
2009-03-27 14:16 ` Eric Sandeen
2009-03-27 23:36   ` Theodore Tso
2009-03-31 13:00     ` Jan Kara
2009-03-27 16:35 ` Aneesh Kumar K.V
2009-03-27 23:20   ` Theodore Tso [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=20090327232045.GH5176@mit.edu \
    --to=tytso@mit.edu \
    --cc=adilger@sun.com \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=error27@gmail.com \
    --cc=linux-ext4@vger.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 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).