From: Renaud Barbier <renaud.barbier@ge.com>
To: Robert Jarzmik <robert.jarzmik@free.fr>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 00/18] UBIFS support
Date: Wed, 05 Dec 2012 11:47:28 +0000 [thread overview]
Message-ID: <50BF3450.50502@ge.com> (raw)
In-Reply-To: <87k3sxzijh.fsf@free.fr>
On 04/12/2012 20:09, Robert Jarzmik wrote:
> Renaud Barbier <renaud.barbier@ge.com> writes:
>
>> On 03/12/2012 19:17, Robert Jarzmik wrote:
>>> Hi Renaud,
>>>
>>> That's a really huge piece of a patchset.
>>>
>>> Please tell me that almost 100% of the code was taken out of the linux
>>> kernel. Even better, are there any patches in there that are linux kernel
>>> copies, so that review is not necessary ?
>> It is actually derived from U-boot which derive it from Linux. It would not be
>> as recent as the Linux code.
>> If you need the code to be fully derived from Linux, then ignore it. This is
>> something
>> I hopefully can work on in the future (N months).
> It's up to Sascha, but I think out of U-boot is fine too. So are all the
> patches a full copy paste of U-boot, or are there specific parts (adaptation) to
> barebox ?
99% of the updates happened in the file ubifs.c. The rest is cosmetic
(super.c):
There is code specific to U-boot that has been reworked:
ubifs_load was the basis to create ubifs_open, ubifs_read, ubifs_close
ubifs_ls was the basis to create ubifs_opendir, ubifs_closedir
ubifs_stat is also derived from U-boot code.
or renamed
ubifs_printdir -> ubifs_doreaddir (similar to Linux code)
There is code added to Barebox:
ubifs_probe, ubifs_remove.
To do:
zlib is commented out. Only lzo support has been tested.
Entry point: there is no 'link' entry point.
>
> I'd think that if you tested the patches succesfully in barebox, and if the
> adaptation is very small, we will review only the adaptation ... hence the
> question, where is the adaptation ?
>
> Cheers.
>
> --
> Robert
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2012-12-05 11:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-03 18:08 Renaud Barbier
2012-12-03 18:08 ` [PATCH 01/18] fs/fs.c: check that fsdev->cdev->dev is not NULL Renaud Barbier
2012-12-03 18:08 ` [PATCH 02/18] UBIFS: preparation Renaud Barbier
2012-12-03 18:08 ` [PATCH 03/18] UBIFS: header files (1/2) Renaud Barbier
2012-12-03 18:08 ` [PATCH 04/18] UBIFS: header files (2/2) Renaud Barbier
2012-12-03 18:08 ` [PATCH 05/18] UBIFS: file operations Renaud Barbier
2012-12-04 22:53 ` Sascha Hauer
2012-12-03 18:08 ` [PATCH 06/18] UBIFS: initialization Renaud Barbier
2012-12-03 18:08 ` [PATCH 07/18] UBIFS: journal Renaud Barbier
2012-12-03 18:08 ` [PATCH 08/18] UBIFS: I/O subsystem Renaud Barbier
2012-12-03 18:08 ` [PATCH 09/18] UBIFS: LEB support Renaud Barbier
2012-12-03 18:08 ` [PATCH 10/18] UBIFS: master node Renaud Barbier
2012-12-03 18:08 ` [PATCH 11/18] UBIFS: recovery Renaud Barbier
2012-12-03 18:08 ` [PATCH 12/18] UBIFS: tree node cache Renaud Barbier
2012-12-03 18:08 ` [PATCH 13/18] UBIFS: superblock Renaud Barbier
2012-12-03 18:08 ` [PATCH 14/18] UBIFS: scan Renaud Barbier
2012-12-03 18:08 ` [PATCH 15/18] UBIFS: configuration and build directives Renaud Barbier
2012-12-03 18:08 ` [PATCH 16/18] ubifs bad superblock bug Renaud Barbier
2012-12-03 18:08 ` [PATCH 17/18] UBIFS: Improve error message when reading superblock failed Renaud Barbier
2012-12-03 18:08 ` [PATCH 18/18] ubifs: Fix memory leak in ubifs_finddir Renaud Barbier
2012-12-03 19:17 ` [PATCH 00/18] UBIFS support Robert Jarzmik
2012-12-04 10:35 ` Renaud Barbier
2012-12-04 20:09 ` Robert Jarzmik
2012-12-05 11:47 ` Renaud Barbier [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=50BF3450.50502@ge.com \
--to=renaud.barbier@ge.com \
--cc=barebox@lists.infradead.org \
--cc=robert.jarzmik@free.fr \
/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