linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Brian Norris" <computersforpeace@gmail.com>
To: "Artem Bityutskiy" <dedekind1@gmail.com>
Cc: Brian Norris <computersforpeace@gmail.com>,
	linux-mtd@lists.infradead.org,
	Mike Frysinger <vapier.adi@gmail.com>
Subject: [PATCH 6/6] nanddump: warn about future default --nooob
Date: Mon, 13 Jun 2011 16:32:03 -0700	[thread overview]
Message-ID: <1308007923-6820-6-git-send-email-computersforpeace@gmail.com> (raw)
In-Reply-To: <1308007923-6820-1-git-send-email-computersforpeace@gmail.com>

To work as a proper inverse to nandwrite, nanddump must not dump OOB data by
default. This patch prints a warning regarding the future change.

Signed-off-by: Brian Norris <computersforpeace@gmail.com>
---
 feature-removal-schedule.txt |    8 ++++++++
 nanddump.c                   |    3 +++
 2 files changed, 11 insertions(+), 0 deletions(-)

diff --git a/feature-removal-schedule.txt b/feature-removal-schedule.txt
index 0f1f5c5..0bb5cb2 100644
--- a/feature-removal-schedule.txt
+++ b/feature-removal-schedule.txt
@@ -65,3 +65,11 @@ Transition summary table:
  --omitbad      --bb=omitbad               dump flash data, substituting nothing for any bad blocks
 
 ---------------------------
+
+5. nanddump will not dump OOB by default
+
+In 1.4.6, nanddump will not dump OOB by default. To dump OOB, you will have to
+explicitly use the option '-o' or '--oob'. For now, there is simply a warning
+every time you use nanddump.
+
+---------------------------
diff --git a/nanddump.c b/nanddump.c
index 211f8ae..9c2e326 100644
--- a/nanddump.c
+++ b/nanddump.c
@@ -355,6 +355,9 @@ int main(int argc, char * const argv[])
 
 	process_options(argc, argv);
 
+	fprintf(stderr, "Warning: in next release, nanddump will not dump OOB"
+			" by default.\n");
+
 	/* Initialize libmtd */
 	mtd_desc = libmtd_open();
 	if (!mtd_desc)
-- 
1.7.0.4

      parent reply	other threads:[~2011-06-13 23:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-13 23:31 [PATCH 1/6] nanddump: add --bb=METHOD option Brian Norris
2011-06-13 23:31 ` [PATCH 2/6] nanddump: remove --skipbad, leaving --bb=skipbad Brian Norris
2011-06-13 23:32 ` [PATCH 3/6] nanddump: deprecation messages for old BB options Brian Norris
2011-06-13 23:32 ` [PATCH 4/6] nanddump: warn about changing default badblock method Brian Norris
2011-06-13 23:32 ` [PATCH 5/6] feature-removal-schedule: describe nanddump changes Brian Norris
2011-06-13 23:32 ` Brian Norris [this message]

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=1308007923-6820-6-git-send-email-computersforpeace@gmail.com \
    --to=computersforpeace@gmail.com \
    --cc=dedekind1@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;
as well as URLs for NNTP newsgroup(s).