From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Ext4 tree backports for 2.6.27.13 and 2.6.28.2
Date: Wed, 11 Feb 2009 13:29:14 +0530 [thread overview]
Message-ID: <20090211075914.GC20842@skywalker> (raw)
In-Reply-To: <E1LT8MN-0003Ps-Ur@closure.thunk.org>
On Sat, Jan 31, 2009 at 12:25:39AM -0500, Theodore Ts'o wrote:
> I've updated the ext4 backport branches on the ext4 git tree:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git
> http://git.kernel.org/?p=linux/kernel/git/tytso/ext4.git
>
> The for-stable branch is branched off of 2.6.28.2, and has a candidate
> set of patches to be included in the next stable release. The
> for-stable-2.6.27 branch is branched off of 2.6.27.13.
>
> I'm more confident with the 2.6.28 stable candidate than the 2.6.27
> stable candidates at the moment, but given that we just missed the
> 2.6.27.14 and 2.6.28.3 release cycles, that should give us plenty of
> time to test the patches.
>
> - Ted
>
>
> 8556e8f3 18d5cb0 fd3bd090
> ext4: Don't allow new groups to be added during block allocation
>
This commit on for-stable-2.6.27 is not complete.
ac->alloc_semp is not assigned in the code.
-aneesh
next prev parent reply other threads:[~2009-02-11 7:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-31 5:25 Ext4 tree backports for 2.6.27.13 and 2.6.28.2 Theodore Ts'o
2009-02-10 23:36 ` Chuck Ebbert
2009-02-11 20:37 ` Chuck Ebbert
2009-02-11 7:59 ` Aneesh Kumar K.V [this message]
2009-02-11 20:33 ` Chuck Ebbert
2009-02-12 21:19 ` Theodore Tso
2009-02-16 21:35 ` Chuck Ebbert
2009-03-31 12:02 ` Fabio Comolli
2009-03-31 12:33 ` Theodore Tso
2009-03-31 12:40 ` Fabio Comolli
2009-03-31 12:47 ` Theodore Tso
2009-03-31 12:50 ` Fabio Comolli
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=20090211075914.GC20842@skywalker \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).