linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Kleikamp <dave.kleikamp@oracle.com>
To: Jan Kara <jack@suse.com>, linux-fsdevel@vger.kernel.org
Cc: jfs-discussion@lists.sourceforge.net
Subject: Re: [PATCH] jfs: clean up jfs_rename and fix out of order unlock
Date: Fri, 17 Jul 2015 11:53:01 -0500	[thread overview]
Message-ID: <55A932ED.1090407@oracle.com> (raw)
In-Reply-To: <55A6ABF7.9010302@oracle.com>

Trimmed the cc list

On 07/15/2015 01:52 PM, Dave Kleikamp wrote:
> Subject: [PATCH] jfs: clean up jfs_rename and fix out of order unlock
> 
> [ Jan, I'll push this right away. You can carry it along until it
> gets merged. I want this pushed to stable as well.]

This is in mainline now. I changed my mind about stable since this
didn't fix an observed problem, but a potential yet unlikely one.

Shaggy

  reply	other threads:[~2015-07-17 16:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-15 12:42 [PATCH 0/6] quota: Propagate errors when creating quota entry Jan Kara
2015-07-15 12:42 ` [PATCH 1/6] quota: Propagate error from ->acquire_dquot() Jan Kara
2015-07-15 12:42 ` [PATCH 2/6] ext2: Handle error from dquot_initalize() Jan Kara
2015-07-15 12:42 ` [PATCH 3/6] ext4: Handle error from dquot_initialize() Jan Kara
2015-07-15 14:20   ` Theodore Ts'o
2015-07-15 12:42 ` [PATCH 4/6] ocfs2: " Jan Kara
2015-07-16  2:35   ` [Ocfs2-devel] " Junxiao Bi
2015-07-15 12:42 ` [PATCH 5/6] jfs: " Jan Kara
2015-07-15 17:23   ` Dave Kleikamp
2015-07-15 17:35     ` Dave Kleikamp
2015-07-15 18:52   ` [PATCH] jfs: clean up jfs_rename and fix out of order unlock Dave Kleikamp
2015-07-17 16:53     ` Dave Kleikamp [this message]
2015-07-15 18:53   ` [PATCH] dquot_initialize() can now return error. Handle it where possible Dave Kleikamp
2015-07-16 10:02     ` Jan Kara
2015-07-15 12:42 ` [PATCH 6/6] reiserfs: Handle error from dquot_initialize() Jan Kara

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=55A932ED.1090407@oracle.com \
    --to=dave.kleikamp@oracle.com \
    --cc=jack@suse.com \
    --cc=jfs-discussion@lists.sourceforge.net \
    --cc=linux-fsdevel@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).