From: Felix Radensky <felix@embedded-sol.com>
To: emre kara <emrekara2002@yahoo.co.uk>
Cc: Wood Scott-B07421 <B07421@freescale.com>,
David Woodhouse <David.Woodhouse@intel.com>,
linux-kernel@vger.kernel.org, bayraktarz@yahoo.com,
Lan Chunhe-B25806 <b25806@freescale.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Scott Wood <scottwood@freescale.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: fsl elbc driver causes corruption with bus monitor timeouts while simultaneously access on Nor / Nand mtd partitions
Date: Thu, 14 Apr 2011 15:10:17 +0300 [thread overview]
Message-ID: <4DA6E429.7010408@embedded-sol.com> (raw)
In-Reply-To: <204286.97927.qm@web25602.mail.ukl.yahoo.com>
[-- Attachment #1: Type: text/html, Size: 1101 bytes --]
prev parent reply other threads:[~2011-04-14 12:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 7:06 fsl elbc driver causes corruption with bus monitor timeouts while simultaneously access on Nor / Nand mtd partitions emre kara
2011-04-14 12:10 ` Felix Radensky [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=4DA6E429.7010408@embedded-sol.com \
--to=felix@embedded-sol.com \
--cc=B07421@freescale.com \
--cc=David.Woodhouse@intel.com \
--cc=b25806@freescale.com \
--cc=bayraktarz@yahoo.com \
--cc=emrekara2002@yahoo.co.uk \
--cc=linux-kernel@vger.kernel.org \
--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).