From: Artem Bityutskiy <dedekind1@gmail.com>
To: Baruch Siach <baruch@tkos.co.il>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] nanddump: warn when the start address is not page aligned
Date: Mon, 18 Oct 2010 13:31:29 +0300 [thread overview]
Message-ID: <1287397889.1972.46.camel@localhost> (raw)
In-Reply-To: <1909cbad57553279212f156a0c7cb20178981909.1287386497.git.baruch@tkos.co.il>
On Mon, 2010-10-18 at 09:23 +0200, Baruch Siach wrote:
> nanddump should be consistent with nandwrite, which does not accept non page
> aligned start addresses. Thus, non page aligned dumps are useless.
>
> To ease migration only warn for now. Add the plan of making this an error to
> feature-removal-schedule.txt.
>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
> feature-removal-schedule.txt | 12 +++++++++++-
> nanddump.c | 7 +++++++
> 2 files changed, 18 insertions(+), 1 deletions(-)
>
> diff --git a/feature-removal-schedule.txt b/feature-removal-schedule.txt
> index 21bc8d4..f4ed2a3 100644
> --- a/feature-removal-schedule.txt
> +++ b/feature-removal-schedule.txt
> @@ -27,5 +27,15 @@ So the plan is (to be done by Artem Bityutskiy):
> 3.1 adding a warning to make users stop using them
> 3.2 removing both options.
> ---------------------------
> -2.
> +2. nanddump: fail when the -s parameter is not page aligned
> +
> +nanddump should be consistent with nandwrite, and refuse accepting non page
> +aligned start addresses. These dumps are most likely useless, since nandwrite
> +won't write then at this location. Currently only a warning is issued to keep
> +backward compatibility during a transition period. This should become an error
> +after 1.5.0.
I tweaked this and removed 1.5.0 - it is better to not specify exact
version. Also, fixed the following trailing white-spaces issue for the
feature-removal-schedule.txt part:
Applying: nanddump: warn when the start address is not page aligned
/home/dedekind/git/mtd-utils/.git/rebase-apply/patch:17: trailing whitespace.
nanddump should be consistent with nandwrite, and refuse accepting non page
/home/dedekind/git/mtd-utils/.git/rebase-apply/patch:18: trailing whitespace.
aligned start addresses. These dumps are most likely useless, since nandwrite
/home/dedekind/git/mtd-utils/.git/rebase-apply/patch:19: trailing whitespace.
won't write then at this location. Currently only a warning is issued to keep
/home/dedekind/git/mtd-utils/.git/rebase-apply/patch:20: trailing whitespace.
backward compatibility during a transition period. This should become an error
warning: 4 lines add whitespace errors.
And pushed, thanks.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
prev parent reply other threads:[~2010-10-18 10:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-12 8:23 [PATCH 1/2] nanddump: verify that start address is page aligned Baruch Siach
2010-10-12 8:23 ` [PATCH 2/2] nanddump: always check the first erase block Baruch Siach
2010-10-16 19:11 ` Artem Bityutskiy
2010-10-16 19:08 ` [PATCH 1/2] nanddump: verify that start address is page aligned Artem Bityutskiy
2010-10-18 7:23 ` [PATCH] nanddump: warn when the start address is not " Baruch Siach
2010-10-18 10:31 ` Artem Bityutskiy [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=1287397889.1972.46.camel@localhost \
--to=dedekind1@gmail.com \
--cc=baruch@tkos.co.il \
--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 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.