All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Brian Norris" <computersforpeace@gmail.com>
To: "Artem Bityutskiy" <dedekind1@gmail.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
	Brian Norris <computersforpeace@gmail.com>,
	linux-mtd@lists.infradead.org,
	Mike Frysinger <vapier.adi@gmail.com>
Subject: [PATCH 0/6] complete nanddump feature-removals
Date: Fri, 24 Jun 2011 11:03:08 -0700	[thread overview]
Message-ID: <1308938594-20486-1-git-send-email-computersforpeace@gmail.com> (raw)

Here's my patchset to complete the feature removals and change of
defaults for nanddump (+ 1 bug fix for integck...). These should
be pushed after the 1.4.5 release.

Thanks,
Brian

Brian Norris (6):
  nanddump: kill --omitbad, --noskipbad
  nanddump: change default to --bb=skipbad
  nanddump: change -o to mean --oob, not --omitoob
  nanddump: default to NOT dumping OOB data
  feature-removal: remove completed tasks
  integck: fix build error (MS_DIRSYNC, MS_RELATIME)

 feature-removal-schedule.txt       |   37 ----------------
 nanddump.c                         |   85 +++++-------------------------------
 tests/fs-tests/integrity/integck.c |    1 +
 3 files changed, 13 insertions(+), 110 deletions(-)

             reply	other threads:[~2011-06-24 18:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-24 18:03 Brian Norris [this message]
2011-06-24 18:03 ` [PATCH 1/6] nanddump: kill --omitbad, --noskipbad Brian Norris
2011-06-24 18:08   ` Brian Norris
2011-06-24 18:03 ` [PATCH 2/6] nanddump: change default to --bb=skipbad Brian Norris
2011-06-24 18:03 ` [PATCH 3/6] nanddump: change -o to mean --oob, not --omitoob Brian Norris
2011-06-24 18:03 ` [PATCH 4/6] nanddump: default to NOT dumping OOB data Brian Norris
2011-06-24 18:03 ` [PATCH 5/6] feature-removal: remove completed tasks Brian Norris
2011-06-24 18:03 ` [PATCH 6/6] integck: fix build error (MS_DIRSYNC, MS_RELATIME) Brian Norris
2011-06-25  7:03 ` [PATCH 0/6] complete nanddump feature-removals 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=1308938594-20486-1-git-send-email-computersforpeace@gmail.com \
    --to=computersforpeace@gmail.com \
    --cc=dedekind1@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.