public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Frank Haverkamp <haver@vnet.ibm.com>
To: Alexander Schmidt <alexs@linux.ibm.com>
Cc: John Smith <john@arrows.demon.co.uk>,
	linux-mtd@lists.infradead.org,
	Frank Haverkamp <haver@linux.vnet.ibm.com>
Subject: Re: UBI Tools - problem with multiple ubi devices.
Date: Wed, 28 Feb 2007 23:08:52 +0100	[thread overview]
Message-ID: <1172700532.3904.5.camel@localhost.localdomain> (raw)
In-Reply-To: <200702281029.34799.alexs@linux.vnet.ibm.com>

Hi Alex & John,

thanks for taking care. I included it in my git. I also reworked my git
to be based on the mtd-utils.git again. I will start there now to use
the ubi branch for the changes we want to try out before Josh can take
them into the offical mtd-utils.git/ubi.

On Wed, 2007-02-28 at 10:29 +0100, Alexander Schmidt wrote:
> On Tuesday 27 February 2007, John Smith wrote:
> > In
> > GIT:      users/haver/mtd-utils.git
> > File:     ubi-utils/src/libubi.c
> > Function: get_ubi_info
> > 
> > The code counts the number of UBI volumes by looking for files called
> > 
> >   /sys/class/ubi0, /sys/class/ubi1, ...
> > 
> > but the files are actually
> > 
> >   /sys/class/ubi/ubi0, ...
> > 
> > The count starts from 1 (probably also wrong), so is usable if there is a
> > single UBI device. But if there is more than one UBI device, tools like
> > ubimkvol fail.

John, thanks for pointing this out. Feel free to send us a patch in
addition to your bug-report. If it works we can immediately include it.
Pleaes let us know if it works for you now.

> 
> Hi John,
> 
> thanks for pointing this out.

> Frank, please review and commit.
> 
Thanks, looks good to me, included.

Frank

  reply	other threads:[~2007-02-28 22:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-27 21:12 UBI Tools - problem with multiple ubi devices John Smith
2007-02-28  9:29 ` Alexander Schmidt
2007-02-28 22:08   ` Frank Haverkamp [this message]
2007-03-07 13:15     ` Josh Boyer
2007-03-14 17:36       ` Josh Boyer

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=1172700532.3904.5.camel@localhost.localdomain \
    --to=haver@vnet.ibm.com \
    --cc=alexs@linux.ibm.com \
    --cc=haver@linux.vnet.ibm.com \
    --cc=john@arrows.demon.co.uk \
    --cc=linux-mtd@lists.infradead.org \
    /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