All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Jan Kara <jack@suse.cz>
Cc: linux-fsdevel@vger.kernel.org, Mark Fasheh <mfasheh@suse.com>,
	Joel Becker <jlbec@evilplan.org>,
	ocfs2-devel@oss.oracle.com, xfs@oss.sgi.com
Subject: Re: [PATCH 1/3] quota: Add support for ->get_nextdqblk() for VFS quota
Date: Fri, 5 Feb 2016 12:05:19 +1100	[thread overview]
Message-ID: <20160205010519.GJ459@dastard> (raw)
In-Reply-To: <1454596087-6814-2-git-send-email-jack@suse.cz>

On Thu, Feb 04, 2016 at 03:28:05PM +0100, Jan Kara wrote:
> Add infrastructure for supporting get_nextdqblk() callback for VFS
> quotas. Translate the operation into a callback to appropriate
> filesystem and consequently to quota format callback.
> 
> Signed-off-by: Jan Kara <jack@suse.cz>

I'm a little confused here. What patchset is this dependent on? i.e.
what introduces the ->get_nextdqblk method?

The patches I currently have in my XFS working tree introduce this
(quota: add new quotactl Q_XGETNEXTQUOTA) and everythign else is
dependent on this. I looked a coupl eof days ago and I wasnt' able
to find this in your tree.

I'd much prefer that one of us publish a stable branch with just the
quotactl() infrastructure (i.e. commands and bits up to the
->get_nextdqblk() callback) that we can then both base the different
subsystem implementations off, rather than one of us having to pull
in a whole tree of changes just to get the one commit we need...

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

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

WARNING: multiple messages have this Message-ID (diff)
From: Dave Chinner <david@fromorbit.com>
To: Jan Kara <jack@suse.cz>
Cc: linux-fsdevel@vger.kernel.org, ocfs2-devel@oss.oracle.com,
	Mark Fasheh <mfasheh@suse.com>, Joel Becker <jlbec@evilplan.org>,
	xfs@oss.sgi.com
Subject: [Ocfs2-devel] [PATCH 1/3] quota: Add support for ->get_nextdqblk() for VFS quota
Date: Fri, 5 Feb 2016 12:05:19 +1100	[thread overview]
Message-ID: <20160205010519.GJ459@dastard> (raw)
In-Reply-To: <1454596087-6814-2-git-send-email-jack@suse.cz>

On Thu, Feb 04, 2016 at 03:28:05PM +0100, Jan Kara wrote:
> Add infrastructure for supporting get_nextdqblk() callback for VFS
> quotas. Translate the operation into a callback to appropriate
> filesystem and consequently to quota format callback.
> 
> Signed-off-by: Jan Kara <jack@suse.cz>

I'm a little confused here. What patchset is this dependent on? i.e.
what introduces the ->get_nextdqblk method?

The patches I currently have in my XFS working tree introduce this
(quota: add new quotactl Q_XGETNEXTQUOTA) and everythign else is
dependent on this. I looked a coupl eof days ago and I wasnt' able
to find this in your tree.

I'd much prefer that one of us publish a stable branch with just the
quotactl() infrastructure (i.e. commands and bits up to the
->get_nextdqblk() callback) that we can then both base the different
subsystem implementations off, rather than one of us having to pull
in a whole tree of changes just to get the one commit we need...

Cheers,

Dave.
-- 
Dave Chinner
david at fromorbit.com

WARNING: multiple messages have this Message-ID (diff)
From: Dave Chinner <david@fromorbit.com>
To: Jan Kara <jack@suse.cz>
Cc: linux-fsdevel@vger.kernel.org, ocfs2-devel@oss.oracle.com,
	Mark Fasheh <mfasheh@suse.com>, Joel Becker <jlbec@evilplan.org>,
	xfs@oss.sgi.com
Subject: Re: [PATCH 1/3] quota: Add support for ->get_nextdqblk() for VFS quota
Date: Fri, 5 Feb 2016 12:05:19 +1100	[thread overview]
Message-ID: <20160205010519.GJ459@dastard> (raw)
In-Reply-To: <1454596087-6814-2-git-send-email-jack@suse.cz>

On Thu, Feb 04, 2016 at 03:28:05PM +0100, Jan Kara wrote:
> Add infrastructure for supporting get_nextdqblk() callback for VFS
> quotas. Translate the operation into a callback to appropriate
> filesystem and consequently to quota format callback.
> 
> Signed-off-by: Jan Kara <jack@suse.cz>

I'm a little confused here. What patchset is this dependent on? i.e.
what introduces the ->get_nextdqblk method?

The patches I currently have in my XFS working tree introduce this
(quota: add new quotactl Q_XGETNEXTQUOTA) and everythign else is
dependent on this. I looked a coupl eof days ago and I wasnt' able
to find this in your tree.

I'd much prefer that one of us publish a stable branch with just the
quotactl() infrastructure (i.e. commands and bits up to the
->get_nextdqblk() callback) that we can then both base the different
subsystem implementations off, rather than one of us having to pull
in a whole tree of changes just to get the one commit we need...

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2016-02-05  1:06 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-04 14:28 [PATCH 0/3 v2] Q_GETNEXTQUOTA support Jan Kara
2016-02-04 14:28 ` Jan Kara
2016-02-04 14:28 ` [Ocfs2-devel] " Jan Kara
2016-02-04 14:28 ` [PATCH 1/3] quota: Add support for ->get_nextdqblk() for VFS quota Jan Kara
2016-02-04 14:28   ` Jan Kara
2016-02-04 14:28   ` [Ocfs2-devel] " Jan Kara
2016-02-05  1:05   ` Dave Chinner [this message]
2016-02-05  1:05     ` Dave Chinner
2016-02-05  1:05     ` [Ocfs2-devel] " Dave Chinner
2016-02-08  6:15     ` Dave Chinner
2016-02-08  6:15       ` Dave Chinner
2016-02-08  6:15       ` [Ocfs2-devel] " Dave Chinner
2016-02-08 14:27     ` Jan Kara
2016-02-08 14:27       ` Jan Kara
2016-02-08 14:27       ` [Ocfs2-devel] " Jan Kara
2016-02-08 14:34       ` Jan Kara
2016-02-08 14:34         ` Jan Kara
2016-02-08 14:34         ` [Ocfs2-devel] " Jan Kara
2016-02-19 17:31   ` Eric Sandeen
2016-02-19 17:31     ` Eric Sandeen
2016-02-19 17:31     ` [Ocfs2-devel] " Eric Sandeen
2016-02-19 18:33     ` Jan Kara
2016-02-19 18:33       ` Jan Kara
2016-02-19 18:33       ` [Ocfs2-devel] " Jan Kara
2016-02-19 18:43       ` Eric Sandeen
2016-02-19 18:43         ` Eric Sandeen
2016-02-19 18:43         ` [Ocfs2-devel] " Eric Sandeen
2016-02-22  8:01         ` Jan Kara
2016-02-22  8:01           ` Jan Kara
2016-02-22  8:01           ` [Ocfs2-devel] " Jan Kara
2016-02-04 14:28 ` [PATCH 2/3] quota_v2: Implement get_next_id() for V2 quota format Jan Kara
2016-02-04 14:28   ` Jan Kara
2016-02-04 14:28   ` [Ocfs2-devel] " Jan Kara
2016-02-04 14:28 ` [PATCH 3/3] ocfs2: Implement get_next_id() Jan Kara
2016-02-04 14:28   ` Jan Kara
2016-02-04 14:28   ` [Ocfs2-devel] " 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=20160205010519.GJ459@dastard \
    --to=david@fromorbit.com \
    --cc=jack@suse.cz \
    --cc=jlbec@evilplan.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=mfasheh@suse.com \
    --cc=ocfs2-devel@oss.oracle.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.