From: Artem Bityutskiy <dedekind1@gmail.com>
To: Shaohui Xie <Shaohui.Xie@freescale.com>
Cc: scottwood@freescale.com, linux-mtd@lists.infradead.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc/85xx: fix NAND_CMD_READID read bytes number
Date: Wed, 22 Jun 2011 08:32:20 +0300 [thread overview]
Message-ID: <1308720745.18119.32.camel@sauron> (raw)
In-Reply-To: <1307931792-30386-1-git-send-email-Shaohui.Xie@freescale.com>
On Mon, 2011-06-13 at 10:23 +0800, Shaohui Xie wrote:
> when nand_get_flash_type() is called, it will read 8 bytes of ID instead of 5,
> but the driver only read 5 bytes, so kernel will dump error messages like:
>
> fsl-lbc ffe124000.localbus: read_byte beyond end of buffer
> fsl-lbc ffe124000.localbus: read_byte beyond end of buffer
> fsl-lbc ffe124000.localbus: read_byte beyond end of buffer
>
Thanks!
--
Best Regards,
Artem Bityutskiy
next prev parent reply other threads:[~2011-06-22 5:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-13 2:23 [PATCH] powerpc/85xx: fix NAND_CMD_READID read bytes number Shaohui Xie
2011-06-17 17:58 ` Bryan Hundven
2011-06-22 5:32 ` Artem Bityutskiy [this message]
2011-06-22 11:08 ` Kumar Gala
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=1308720745.18119.32.camel@sauron \
--to=dedekind1@gmail.com \
--cc=Shaohui.Xie@freescale.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=scottwood@freescale.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).