From: Artem Bityutskiy <dedekind1@gmail.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
linux-mtd@lists.infradead.org,
Mike Frysinger <vapier.adi@gmail.com>
Subject: Re: [PATCH v2 2/3] mtd-utils: nanddump: Dynamic buffer, increase pagesize/oobsize
Date: Sun, 17 Oct 2010 11:00:34 +0300 [thread overview]
Message-ID: <1287302434.1951.2.camel@localhost> (raw)
In-Reply-To: <1287189331-9475-1-git-send-email-computersforpeace@gmail.com>
On Fri, 2010-10-15 at 17:35 -0700, Brian Norris wrote:
> The buffers used for dumping page and OOB data needed dynamic
> allocation to help eliminate burdens for updating (i.e., every
> time there's a new OOB size we don't have to increase the sizes).
>
> Also, there is no need to check flash chips for "standard sizes."
> With recent changes to the printing codebase, we should be able to
> handle arbitrary sizes with no problem.
>
> More exit operations are now necessary on program failure, so
> "goto closeall" is used more liberally.
>
> Also, common.h is included for the use of xmalloc.
>
> Signed-off-by: Brian Norris <computersforpeace@gmail.com>
> ---
Patches did not apply cleanly, but I've resolved conflicts an pushed
them, thank you.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2010-10-17 8:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTi%3DXdvN2vGu7Z5M7jj%3Dz_qrx%3D9F93WiDnPYkcDgY@mail.gmail.com>
2010-10-16 0:35 ` [PATCH v2 2/3] mtd-utils: nanddump: Dynamic buffer, increase pagesize/oobsize Brian Norris
2010-10-16 19:34 ` Artem Bityutskiy
2010-10-17 8:00 ` Artem Bityutskiy [this message]
2010-10-17 16:19 ` Brian Norris
2010-10-17 18:03 ` Artem Bityutskiy
2010-10-17 18:23 ` 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=1287302434.1951.2.camel@localhost \
--to=dedekind1@gmail.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.