From: "Jörn Engel" <joern@logfs.org>
To: Josh Boyer <jwboyer@gmail.com>, linux-mtd@lists.infradead.org
Subject: Re: [Patch] Support large devices for flash_eraseaal
Date: Tue, 7 Jul 2009 18:25:43 +0200 [thread overview]
Message-ID: <20090707162543.GB26579@logfs.org> (raw)
In-Reply-To: <20090707162231.GA26579@logfs.org>
On Tue, 7 July 2009 18:22:32 +0200, Jörn Engel wrote:
>
> +static int get_info(const char *devname, struct mtd_info_user64 *mtd64)
> +static int do_erase(int fd, struct erase_info_user64 *ei64, struct mtd_info_user64 *mtd64)
Thinking about it, these two functions probably ought to go into a
library of some sorts. I just used flash_eraseall as a proof-of-concept
test program, so my interest in this area is exhausted. But maybe
someone else feels young and energetic. :)
Jörn
--
Sometimes, asking the right question is already the answer.
-- Unknown
next prev parent reply other threads:[~2009-07-07 16:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-07 14:03 mtd-utils warnings Jörn Engel
2009-07-07 16:22 ` [Patch] Support large devices for flash_eraseaal Jörn Engel
2009-07-07 16:25 ` Jörn Engel [this message]
2009-07-07 16:29 ` 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=20090707162543.GB26579@logfs.org \
--to=joern@logfs.org \
--cc=jwboyer@gmail.com \
--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