From: Artem Bityutskiy <dedekind@infradead.org>
To: Hamish Moffatt <hamish@cloud.net.au>
Cc: linux-mtd@lists.infradead.org
Subject: Re: ubiupdatevol from pipe/compressed file
Date: Tue, 20 May 2008 14:19:21 +0300 [thread overview]
Message-ID: <1211282361.31023.1.camel@sauron> (raw)
In-Reply-To: <20080520083957.GA29998@cloud.net.au>
Hi,
the patch looks good.
On Tue, 2008-05-20 at 18:39 +1000, Hamish Moffatt wrote:
> Actually, it looks like the kernel (drivers/mtd/ubi/upd.c) doesn't
> require the data in whole LEB chunks anyway, so this code could be
> revert with the check for a whole LEB worth of read() removed. I can
> send an updated patch tomorrow.
Yes, UBI accepts any amount of bytes at a time.
>
> My ubiupdatevol.c original may be out of date. If so I can rebase
> tomorrow.
OK, thanks.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2008-05-20 11:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 8:47 ubiupdatevol from pipe/compressed file Hamish Moffatt
2008-05-19 8:54 ` Artem Bityutskiy
2008-05-20 8:39 ` Hamish Moffatt
2008-05-20 11:19 ` Artem Bityutskiy [this message]
2008-05-20 11:53 ` Artem Bityutskiy
2008-06-27 14:36 ` 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=1211282361.31023.1.camel@sauron \
--to=dedekind@infradead.org \
--cc=hamish@cloud.net.au \
--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