From: Artem Bityutskiy <dedekind@infradead.org>
To: Nancy <nancydreaming@gmail.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: Is there possible to integrate mtd ubi ubifs latest version in one git tree?
Date: Sat, 12 Apr 2008 12:59:29 +0300 [thread overview]
Message-ID: <1207994369.5965.126.camel@sauron> (raw)
In-Reply-To: <1207994233.5965.124.camel@sauron>
On Sat, 2008-04-12 at 12:57 +0300, Artem Bityutskiy wrote:
> > If the answer is no, will ubifs give patches for porting it to old
> > linux kernel? The patches only contain the ubifs needed file.
> We maintain 2.6.21, 2.6.22, 2.6.23, and 2.6.24 ports. They contain UBIFS
> patches and all the other patches which are needed to make UBIFS work.
> For example, 2.6.21 port has tons of UBI patches back-ported from the
> ubi-2.6.git tree, it has LZO compressor ported from older versions of
> the kernel as well.
Corrections:
1. Well, 2.6.21 did not have UBI at all, so ubifs-v2.6.21.git contains
all UBI patches, not just UBIFS.
2. LZO was ported from newer kernels of course, not from older.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2008-04-12 10:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-11 6:48 Is there possible to integrate mtd ubi ubifs latest version in one git tree? Nancy
2008-04-12 9:57 ` Artem Bityutskiy
2008-04-12 9:59 ` Artem Bityutskiy [this message]
2008-04-12 10:10 ` Artem Bityutskiy
2008-04-14 4:46 ` Nancy
2008-04-14 9:05 ` Artem Bityutskiy
2008-04-15 11:41 ` Jamie Lokier
2008-04-15 11:44 ` Artem Bityutskiy
2008-04-15 15:21 ` Jamie Lokier
2008-04-15 15:41 ` Artem Bityutskiy
[not found] ` <bae050c10804140435v5141dec6qd61b325a4a1ff6ad@mail.gmail.com>
[not found] ` <1208173090.5965.187.camel@sauron>
2008-04-15 12:04 ` Nancy
2008-04-16 6:11 ` Artem Bityutskiy
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=1207994369.5965.126.camel@sauron \
--to=dedekind@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=nancydreaming@gmail.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