From: Al Viro <viro@ZenIV.linux.org.uk>
To: Mark Fasheh <mfasheh@suse.de>
Cc: Richard Weinberger <richard@nod.at>,
ocfs2-devel@oss.oracle.com, ocfs2-user@oss.oracle.com,
linux-kernel@vger.kernel.org, jlbec@evilplan.org,
linux-fsdevel@vger.kernel.org, david@sigma-star.at
Subject: [Ocfs2-devel] OCFS2 mainline state?
Date: Mon, 25 Feb 2013 21:16:18 +0000 [thread overview]
Message-ID: <20130225211617.GF4503@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20130225211103.GA13510@wotan.suse.de>
On Mon, Feb 25, 2013 at 01:11:03PM -0800, Mark Fasheh wrote:
> I've seen that patch actually and yes it should have been in mainline
> already. I didn't see whether it's in -mm (Andrew is pickup up some of the
> patches for us right now).
>
> I'll check and if it's not I'll try to send him a version of it today.
Normally filesystem trees are fed to Linus... Or I can pick that patch via
VFS tree (and send it to Linus tomorrow). There also had been Jan's ocfs2
patch a while ago; I picked only the VFS part of that series, ext* and
IIRC xfs ones went to corresponding filesystem trees. Should I just pick
the ocfs2 stuff from now on?
WARNING: multiple messages have this Message-ID (diff)
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Mark Fasheh <mfasheh@suse.de>
Cc: Richard Weinberger <richard@nod.at>,
ocfs2-devel@oss.oracle.com, ocfs2-user@oss.oracle.com,
linux-kernel@vger.kernel.org, jlbec@evilplan.org,
linux-fsdevel@vger.kernel.org, david@sigma-star.at
Subject: Re: OCFS2 mainline state?
Date: Mon, 25 Feb 2013 21:16:18 +0000 [thread overview]
Message-ID: <20130225211617.GF4503@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20130225211103.GA13510@wotan.suse.de>
On Mon, Feb 25, 2013 at 01:11:03PM -0800, Mark Fasheh wrote:
> I've seen that patch actually and yes it should have been in mainline
> already. I didn't see whether it's in -mm (Andrew is pickup up some of the
> patches for us right now).
>
> I'll check and if it's not I'll try to send him a version of it today.
Normally filesystem trees are fed to Linus... Or I can pick that patch via
VFS tree (and send it to Linus tomorrow). There also had been Jan's ocfs2
patch a while ago; I picked only the VFS part of that series, ext* and
IIRC xfs ones went to corresponding filesystem trees. Should I just pick
the ocfs2 stuff from now on?
next prev parent reply other threads:[~2013-02-25 21:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-25 20:33 OCFS2 mainline state? Richard Weinberger
2013-02-25 21:11 ` [Ocfs2-devel] " Mark Fasheh
2013-02-25 21:11 ` Mark Fasheh
2013-02-25 21:16 ` Al Viro [this message]
2013-02-25 21:16 ` Al Viro
2013-02-25 21:28 ` [Ocfs2-devel] " Mark Fasheh
2013-02-25 21:28 ` Mark Fasheh
2013-03-02 10:05 ` [Ocfs2-devel] " Joel Becker
2013-03-02 10:05 ` Joel Becker
2013-02-25 21:30 ` [Ocfs2-devel] " Mark Fasheh
2013-02-25 21:30 ` Mark Fasheh
2013-02-25 21:30 ` Mark Fasheh
2013-02-25 21:37 ` [Ocfs2-devel] " Smart Weblications GmbH - Florian Wiessner
2013-02-25 21:37 ` Smart Weblications GmbH - Florian Wiessner
2013-03-02 10:15 ` [Ocfs2-devel] " Vincent ETIENNE
2013-03-02 10:15 ` Vincent ETIENNE
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=20130225211617.GF4503@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=david@sigma-star.at \
--cc=jlbec@evilplan.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mfasheh@suse.de \
--cc=ocfs2-devel@oss.oracle.com \
--cc=ocfs2-user@oss.oracle.com \
--cc=richard@nod.at \
/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.