From: Artem Bityutskiy <dedekind@infradead.org>
To: naveen yadav <yad.naveen@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: UBIFS porting on onenand and on kernel 2.6.18
Date: Fri, 05 Jun 2009 15:22:27 +0300 [thread overview]
Message-ID: <1244204547.5847.57.camel@localhost.localdomain> (raw)
In-Reply-To: <9bde694e0906040504l4742b818p8fd3223dda719f31@mail.gmail.com>
On Thu, 2009-06-04 at 17:34 +0530, naveen yadav wrote:
> Hi all,
>
> i want to port UBIFS to my target board which is running on Linux
>
> 2.6.18. and having samsung onenand.I want to check the performance of
> UBIFS. I need some idea.
>
> shall i take UBI and UBIFS code from latest kernel source tree i.e
> 2.6.29. or shall i use GIT backward patch 2.6.24
> so which way is easy and best.
The easiest will be to start from the old and now unsupported 2.6.21
back-port:
http://git.infradead.org/users/dedekind/ubifs-v2.6.21.git
Then you should port the patches which are missing in the 2.6.21
back-port from the 2.6.24 back-port. This is the easiest way
to go, IMO.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
prev parent reply other threads:[~2009-06-05 12:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9bde694e0906020308r60e7627akcc01ed54bf63914c@mail.gmail.com>
2009-06-04 12:04 ` UBIFS porting on onenand and on kernel 2.6.18 naveen yadav
2009-06-05 12:22 ` Artem Bityutskiy [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=1244204547.5847.57.camel@localhost.localdomain \
--to=dedekind@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=yad.naveen@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