From: Philby John <pjohn@mvista.com>
To: Brian Norris <norris@broadcom.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mtd-www doc, FAQ, general: spelling fixes
Date: Thu, 24 Jun 2010 19:22:02 +0530 [thread overview]
Message-ID: <1277387522.24980.6.camel@localhost.localdomain> (raw)
In-Reply-To: <1277332946-14580-1-git-send-email-norris@broadcom.com>
On Wed, 2010-06-23 at 15:42 -0700, Brian Norris wrote:
> Several spelling, word choice, etc. edits throughout
>
> Signed-off-by: Brian Norris <norris@broadcom.com>
> ---
> doc/general.xml | 2 +-
> doc/nand.xml | 60 +++++++++++++++++++++++++++---------------------------
> doc/onenand.xml | 18 ++++++++--------
> doc/ubi.xml | 14 ++++++------
> doc/ubifs.xml | 18 ++++++++--------
> faq/general.xml | 6 ++--
> faq/jffs2.xml | 18 ++++++++--------
> faq/nand.xml | 14 ++++++------
> faq/ubi.xml | 48 ++++++++++++++++++++++----------------------
> faq/ubifs.xml | 48 ++++++++++++++++++++++----------------------
> source.xml | 2 +-
> 11 files changed, 124 insertions(+), 124 deletions(-)
>
> diff --git a/doc/general.xml b/doc/general.xml
> index e170ace..4e1bfdd 100644
> --- a/doc/general.xml
> +++ b/doc/general.xml
> @@ -122,7 +122,7 @@ git://git.infradead.org/users/ahunter/nand-tests.git
> and nasty DMA issues on an OMAP2 board with OneNAND flash, just by
> running this tests for few hours.</li>
>
> - <li><b>mtd_nandecctest</b>: a simple test that checks correctess of the
> + <li><b>mtd_nandecctest</b>: a simple test that checks correctness of the
> built-in software ECC for 256 and 512-byte buffers; this test is not
> driver-specific but tests general NAND support code.</li>
> </ul>
> diff --git a/doc/nand.xml b/doc/nand.xml
> index 549827b..776f891 100644
> --- a/doc/nand.xml
> +++ b/doc/nand.xml
> @@ -16,8 +16,8 @@ NAND and NOR Flash is the bus interface. NOR Flash is connected to a address / d
> bus direct like other memory devices as SRAM etc. NAND Flash uses a multiplexed I/O
> Interface with some additional control pins. NAND flash is a sequential access device
> appropriate for mass storage applications, while NOR flash is a random access device
> - appropriate for code storage application.NOR Flash can be used for code storage and
> - code execution. Code stored on NAND Flash can't be executed frome there. It must be
> + appropriate for code storage application. NOR Flash can be used for code storage and
> + code execution. Code stored on NAND Flash can't be executed from there. It must be
> loaded into RAM memory and executed from there.</p>
<-snip->
> Probably because you flash is too small? Try to use JFFS2 then, becasue it
^^^ ^^^^^
You missed "you", should be "your", and "becasue".
Regards,
Philby
next prev parent reply other threads:[~2010-06-24 13:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-23 22:42 [PATCH] mtd-www doc, FAQ, general: spelling fixes Brian Norris
2010-06-24 13:52 ` Philby John [this message]
2010-06-24 16:41 ` Brian Norris
2010-07-08 9:24 ` Artem Bityutskiy
2010-07-08 22:23 ` Brian Norris
2010-07-18 7:24 ` Artem Bityutskiy
2010-07-13 8:10 ` 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=1277387522.24980.6.camel@localhost.localdomain \
--to=pjohn@mvista.com \
--cc=linux-mtd@lists.infradead.org \
--cc=norris@broadcom.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).