public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Eric Sandeen <sandeen@redhat.com>,
	Eric Sandeen <sandeen@sandeen.net>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH] xfs: fix Q_XQUOTARM ioctl
Date: Sun, 4 May 2014 10:21:19 +1000	[thread overview]
Message-ID: <20140504002119.GM26353@dastard> (raw)
In-Reply-To: <20140503151440.GA28608@infradead.org>

On Sat, May 03, 2014 at 08:14:40AM -0700, Christoph Hellwig wrote:
> On Sat, May 03, 2014 at 09:36:05AM -0500, Eric Sandeen wrote:
> > Whoops, missed reply-all.
> > 
> > Yes, it will fail this way w/o the kernel patch.
> > 
> > User quota gets removed OK because flags accidentally line up;
> > group quota remains, so you'd see exactly this.
> 
> Ok.  Dave, can you pick it up for for-next?

It's in my queue - I've been trying to get everything sorted for a
3.15-rc4 update first before pushing more 3.16 changes into
for-next. That's been going round in circles on the
truncate_setsize() issue, but I think that is sorted now so it'll be
done soon. ;)

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      reply	other threads:[~2014-05-04  0:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-21 20:33 [PATCH] xfs: fix Q_XQUOTARM ioctl Eric Sandeen
2014-04-22  6:43 ` Christoph Hellwig
2014-04-22 15:54   ` Eric Sandeen
2014-04-22 18:48 ` [PATCH V2] " Eric Sandeen
2014-04-22 21:30   ` Dave Chinner
2014-04-22 21:48     ` Jan Kara
2014-04-23 15:27   ` Christoph Hellwig
2014-04-23 15:28     ` Eric Sandeen
2014-04-23 15:39       ` Christoph Hellwig
2014-05-03 11:48 ` [PATCH] " Christoph Hellwig
2014-05-03 14:36   ` Eric Sandeen
2014-05-03 15:14     ` Christoph Hellwig
2014-05-04  0:21       ` Dave Chinner [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=20140504002119.GM26353@dastard \
    --to=david@fromorbit.com \
    --cc=hch@infradead.org \
    --cc=sandeen@redhat.com \
    --cc=sandeen@sandeen.net \
    --cc=xfs@oss.sgi.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