From: Artem Bityutskiy <dedekind@infradead.org>
To: Corentin Chary <corentin.chary@gmail.com>
Cc: linux-mtd@lists.infradead.org, vapier.adi@gmail.com
Subject: Re: [PATCH 1/2] mkfs.ubifs: UBI I/O Library
Date: Fri, 08 May 2009 17:06:35 +0300 [thread overview]
Message-ID: <1241791595.27996.98.camel@localhost.localdomain> (raw)
In-Reply-To: <71cd59b00905080658n140ca7a6l2c818aea5b6a93d8@mail.gmail.com>
On Fri, 2009-05-08 at 15:58 +0200, Corentin Chary wrote:
> On Fri, May 8, 2009 at 2:20 PM, Artem Bityutskiy <dedekind@infradead.org> wrote:
> > On Fri, 2009-05-08 at 14:07 +0200, Corentin Chary wrote:
> >> No, not really, libubiio provide what you can find in ubi.h, nothing
> >> more (open/close/read/write/change/erase/map/unmap).
> >> There some code in common to read sysfs properties, it's all.
> >> There is libubiio_int.h with some duplicate code from
> >> ubi-utils/src/common.h which could be removed.
> >> libubi on the other hand provide functions to manipulate volume and
> >> devices (rename, create, etc..).
> >
> > Still, what's the reason to have a separate library?
> > Why not to add your stuff to existing one? If there
> > are some issues in libubi, they could be fixed. I just
> > see a lot of common code.
>
> When we made libubiio we wanted something close to the kernel API,
> libubi is not.
But it should not be difficult to change this. You may amend
the API to serve better your purposes.
> To make mkfs.ubifs works with smaller changes, I can add the
> "is_mapped" and "erase" functions to libubi, forgetting the original
> UBI API.
> Does that seems better to you ? If it's ok then I'll do that.
As you wish. I just think we should try not to copy code, but
integrate to the existing code base. If the existing one is
not suitable - fix it.
> >> But the current tree/build system make it hard to share code between
> >> ubi-utils/mtd-utils/mkfs. It what
> >> If you check, there is also three crc32.c/h in mtd-utils ...
> >> (See http://git.iksaif.net/?p=users/iksaif/mtd-utils.git;a=tree;hb=HEAD
> >> to check what a clean tree could be)
> >
> > But surely you may try to re-arrange the tree, make it saner?
> It's what I did on my git tree.. but it only works with CMake.
> I don't know how to fix the current mess with simples Makefiles.
> Maybe someone with better Make skills could help us here ?
You want to move headers from ubi-utils/include to include ?
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2009-05-08 14:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-07 10:21 [PATCH 0/2] mkfs.ubifs and libubiio Corentin Chary
2009-05-07 10:21 ` [PATCH 1/2] mkfs.ubifs: UBI I/O Library Corentin Chary
2009-05-07 10:21 ` [PATCH 2/2] mkfs.ubifs: format directly ubi volume using libubiio Corentin Chary
2009-05-08 8:49 ` [PATCH 1/2] mkfs.ubifs: UBI I/O Library Artem Bityutskiy
2009-05-08 12:07 ` Corentin Chary
2009-05-08 12:20 ` Artem Bityutskiy
2009-05-08 13:58 ` Corentin Chary
2009-05-08 14:06 ` Artem Bityutskiy [this message]
2009-05-08 14:14 ` Artem Bityutskiy
2009-05-08 14:59 ` Corentin Chary
2009-05-08 18:58 ` Mike Frysinger
2009-05-08 19:41 ` Corentin Chary
2009-05-08 20:25 ` Mike Frysinger
2009-05-08 20:32 ` Corentin Chary
2009-05-08 20:36 ` Mike Frysinger
2009-05-07 11:59 ` [PATCH 0/2] mkfs.ubifs and libubiio Corentin Chary
2009-05-07 12:57 ` Josh Boyer
2009-05-07 13:29 ` Corentin Chary
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=1241791595.27996.98.camel@localhost.localdomain \
--to=dedekind@infradead.org \
--cc=corentin.chary@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=vapier.adi@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