From: Andrew Morton <akpm@linux-foundation.org>
To: Joel Becker <Joel.Becker@oracle.com>
Cc: Louis Rilling <louis.rilling@kerlabs.com>,
linux-kernel@vger.kernel.org, ocfs2-devel@oss.oracle.com,
linux-next@vger.kernel.org
Subject: Re: [BUGFIX][PATCH v2 0/2] configfs: Fix cleanup after mkdir() failure
Date: Fri, 11 Jul 2008 15:52:38 -0700 [thread overview]
Message-ID: <20080711155238.f3e257b0.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080711220740.GC22577@mail.oracle.com>
On Fri, 11 Jul 2008 15:07:40 -0700 Joel Becker <Joel.Becker@oracle.com> wrote:
> Ok, I've merged all this work. Please check out my configfs-ALL
> branch and make sure I have everything we've worked on.
>
> http://oss.oracle.com/git/?p=jlbec/linux-2.6.git;a=shortlog;h=configfs-ALL
> git://oss.oracle.com/git/jlbec/linux-2.6.git configfs-ALL
Can you please arrange to get this tree into linux-next?
Thanks.
next prev parent reply other threads:[~2008-07-11 22:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-04 14:56 [BUGFIX][PATCH v2 0/2] configfs: Fix cleanup after mkdir() failure Louis Rilling
2008-07-04 14:56 ` [BUGFIX][PATCH v2 1/2] configfs: Prevent userspace from creating new entries under attaching directories Louis Rilling
2008-07-11 20:02 ` Joel Becker
2008-07-04 14:56 ` [BUGFIX][PATCH v2 2/2] configfs: Lock new directory inodes before removing on cleanup after failure Louis Rilling
2008-07-11 20:05 ` Joel Becker
2008-07-04 16:32 ` [BUGFIX][PATCH v2 0/2] configfs: Fix cleanup after mkdir() failure Louis Rilling
2008-07-06 1:03 ` Joel Becker
2008-07-11 22:07 ` Joel Becker
2008-07-11 22:52 ` Andrew Morton [this message]
2008-07-11 23:37 ` Joel Becker
2008-07-16 13:08 ` Louis Rilling
2008-07-16 17:27 ` Joel Becker
2008-07-16 17:56 ` Louis Rilling
2008-07-16 20:43 ` Joel Becker
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=20080711155238.f3e257b0.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Joel.Becker@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=louis.rilling@kerlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox