From: Artem Bityutskiy <dedekind1@gmail.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: linux-mtd@lists.infradead.org, Mike Frysinger <vapier.adi@gmail.com>
Subject: Re: nanddump badblock options
Date: Wed, 22 Jun 2011 07:42:38 +0300 [thread overview]
Message-ID: <1308717762.18119.21.camel@sauron> (raw)
In-Reply-To: <BANLkTimU-fzEj6ByC9X6DX=tUQ0ay_eYrQ@mail.gmail.com>
On Mon, 2011-06-13 at 12:17 -0700, Brian Norris wrote:
> One last idea, while I'm trying to bring nanddump and nandwrite a
> little closer together:
>
> It makes sense for nanddump and nandwrite to have the same defaults
> regarding OOB. Right now, nandwrite doesn't write OOB by default, and
> nanddump dumps OOB by default. Is it OK to unify this and make
> nanddump default to *not* dumping OOB? Then the nanddump '-o' and
> '--oob' options would stand for 'Dump OOB data'. Unfortunately, this
> makes the '-o' option completely reverse its meaning...
Yes, I think so. Just invent a sensible "deprecation period" plan and go
ahead with unifying them.
Thanks!
--
Best Regards,
Artem Bityutskiy
next prev parent reply other threads:[~2011-06-22 4:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 20:01 nanddump badblock options Brian Norris
2011-06-09 8:26 ` Artem Bityutskiy
2011-06-13 19:17 ` Brian Norris
2011-06-22 4:42 ` Artem Bityutskiy [this message]
2011-06-22 16:53 ` Brian Norris
2011-06-20 19:22 ` Mike Frysinger
2011-06-20 23:09 ` Brian Norris
2011-06-21 0:13 ` Mike Frysinger
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=1308717762.18119.21.camel@sauron \
--to=dedekind1@gmail.com \
--cc=computersforpeace@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