From: Fabio Comolli <fabio.comolli@gmail.com>
To: Theodore Tso <tytso@mit.edu>,
Fabio Comolli <fabio.comolli@gmail.com>,
Chuck Ebbert <cebbert@redhat.com>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
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: Tue, 31 Mar 2009 14:50:49 +0200 [thread overview]
Message-ID: <b637ec0b0903310550x52a22e22hb034ee7aaa0c3844@mail.gmail.com> (raw)
In-Reply-To: <20090331124716.GG13356@mit.edu>
Hi Ted.
On Tue, Mar 31, 2009 at 2:47 PM, Theodore Tso <tytso@mit.edu> wrote:
> On Tue, Mar 31, 2009 at 02:40:22PM +0200, Fabio Comolli wrote:
>> OK. Now I have on my box the 2.6.27.19 kernel. Do you mean that I have
>> to apply 19->20, 20->21 and then this patch?
>
> There are ext4-related fixes in the 19->20 patches. There are no ext4
> related patches in 20->21, so whether or not you do this is optional
> (from the perspective of applying this patch).
>
OK
>> Then mount the fs as ext4dev?
>
> Yes, same as before. I will note that there were some enhancements
> and some lower-priority bug fixes that don't get backported to 2.6.27
> series, since sometimes it is extremely difficult to backport things
> as far as 2.6.27. So if your goal is to use this in production,
> 2.6.29 will almost certainly be a better bet. The number of people
> who test the 2.6.27 backports of ext4 are also much smaller. We
> provide it as a service those who for whatever reason refuse to update
> to newer kernels, but it's hard for me to offer guarantees.
>
Many thanks. I normally use 2.6.29 with ext4 but I just discovered a
bug that prevents me to use video acceleration. It seems that this was
introduced in the 2.6.28 series and 2.6.27.X don't have it.
> Best regards,
>
> - Ted
>
Regards,
Fabio
prev parent reply other threads:[~2009-03-31 12:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-31 5:25 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
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 [this message]
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=b637ec0b0903310550x52a22e22hb034ee7aaa0c3844@mail.gmail.com \
--to=fabio.comolli@gmail.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=cebbert@redhat.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
Powered by JetHome