All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Fasheh <mfasheh@suse.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 00/00] Implement quotas for OCFS2 (version 2)
Date: Thu, 30 Oct 2008 16:32:34 -0700	[thread overview]
Message-ID: <20081030233234.GL15154@wotan.suse.de> (raw)
In-Reply-To: <20081030050254.GA1138@duck.suse.cz>

On Thu, Oct 30, 2008 at 06:02:54AM +0100, Jan Kara wrote:
> On Wed 29-10-08 15:58:32, Mark Fasheh wrote:
> > On Sat, Oct 25, 2008 at 12:05:04AM +0200, Jan Kara wrote:
> > > Hello,
> > > 
> > > the following patch series implements quotas for OCFS2. The patch
> > > series is based on:
> > > git://git.kernel.org/pub/scm/linux/kernel/git/mfasheh/ocfs2.git linux-next
> > 
> > Great, thanks for posting these again.
> > 
> > > I've adressed Joel's comments, also node recovery is now fully working
> > > and I've fixed a few issues I found during my testing. So I'm currently
> > > not aware of any bugs. Please review, test, comment. Thanks.
> > 
> > How are we going to handle the vfs patches? I think realistically, they
> > should just all go into the merge_window branch of ocfs2.git along with the
> > Ocfs2 patches to add quoata support (and make use of the VFS features you
> > added). The VFS patches at least though, should probably get posted to
> > linux-fsdevel before I pick them up.
>   Yup. I don't know if you've noticed but I've already sent majority of VFS
> patches to Andrew Morton (linux-fsdevel CC'd) and they are in -mm. He had
> some valuable comments and other people also tripped onto various minor
> problems. I'm now incorporating all the changes and will send next version
> of the patchset when I'm done.

Oh, ok great!


> Finally, I think it's the easiest if the patches go to Linus via your
> tree. Probably I'll push via that path also 64-bit quota format patch
> although it has nothing to do with OCFS2, since otherwise we would have to
> synchronize unnecessarily.

Yeah, that sounds good. Once they're all ready, we'll move it over to
ocfs2.git. I certainly don't mind carrying any other patches for you either.
	--Mark

--
Mark Fasheh

  reply	other threads:[~2008-10-30 23:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-24 22:05 [Ocfs2-devel] [PATCH 00/00] Implement quotas for OCFS2 (version 2) Jan Kara
2008-10-27  7:22 ` tristan.ye
2008-10-27  9:08 ` tristan.ye
2008-10-27 11:23   ` Jan Kara
2008-10-27 11:23     ` Jan Kara
     [not found]     ` <1225159789.6555.24.camel@tristan-laptop.cn.oracle.com>
2008-10-28 11:23       ` tristan.ye
2008-10-29  1:57         ` Jan Kara
2008-10-29  2:32           ` tristan.ye
2008-10-29 22:58 ` Mark Fasheh
2008-10-30  5:02   ` Jan Kara
2008-10-30 23:32     ` Mark Fasheh [this message]
2008-11-06  1:09 ` Mark Fasheh
2008-11-20 19:33   ` Jan Kara
2008-11-24 20:50     ` Mark Fasheh
  -- strict thread matches above, loose matches on Subject: below --
2008-10-24 22:07 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=20081030233234.GL15154@wotan.suse.de \
    --to=mfasheh@suse.com \
    --cc=ocfs2-devel@oss.oracle.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.