From: Kevin Hilman <khilman@deeprootsystems.com>
To: Cliff Brake <cliff.brake@gmail.com>
Cc: "Ghorai, Sukumar" <s-ghorai@ti.com>,
Linux OMAP Users <linux-omap@vger.kernel.org>,
"Kamat, Nishant" <nskamat@ti.com>
Subject: Re: NAND ECC in linux-omap
Date: Thu, 19 Aug 2010 17:27:33 -0700 [thread overview]
Message-ID: <8762z6f7re.fsf@deeprootsystems.com> (raw)
In-Reply-To: <AANLkTik4+gApkw5fQ561QnJPLX5ED7oN3oU0P6F0+Gsv@mail.gmail.com> (Cliff Brake's message of "Wed, 18 Aug 2010 11:45:31 -0400")
Cliff Brake <cliff.brake@gmail.com> writes:
> On Wed, Aug 18, 2010 at 12:14 AM, Ghorai, Sukumar <s-ghorai@ti.com> wrote:
>> [Ghorai]
>> 1. Can you send the git tree link and branch you are referring?
>
> git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm.git
> branch: pm
> 95e42b92313f229cbc9fc81bf68fe60aaee515aa
>
> I'm pretty sure this branch tracks linux-omap.
Yes, it does.
> I have not tested
> linux-omap yet (git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git:master)
the PM branch has nothing NAND/MTD related in it, so the problem should
be the same on linux-omap, but should be tested there as well to
eliminate any possible PM interactions.
Kevin
next prev parent reply other threads:[~2010-08-20 0:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-17 21:56 NAND ECC in linux-omap Cliff Brake
2010-08-18 4:14 ` Ghorai, Sukumar
2010-08-18 15:45 ` Cliff Brake
2010-08-20 0:27 ` Kevin Hilman [this message]
2010-08-24 13:51 ` Ghorai, Sukumar
2010-08-24 14:34 ` Cliff Brake
2010-08-24 17:10 ` Vimal Singh
[not found] ` <2A3DCF3DA181AD40BDE86A3150B27B6B031584E052@dbde02.ent.ti.com>
[not found] ` <AANLkTi=n_ojiG=BY0AskW-AhTX1mt2hxauLxDSvyfh4b@mail.gmail.com>
[not found] ` <AANLkTik3MADx8Vvp2z_KqqEG=oJEV8AQENMELCbAchBY@mail.gmail.com>
[not found] ` <AANLkTinr_0iX9RyJ=S_0c7YL84LJX3q1anqWp16DMW_K@mail.gmail.com>
2010-08-27 20:36 ` Vimal Singh
2010-08-27 20:36 ` Vimal Singh
2010-08-28 20:09 ` Ghorai, Sukumar
2010-08-28 20:09 ` Ghorai, Sukumar
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=8762z6f7re.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=cliff.brake@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=nskamat@ti.com \
--cc=s-ghorai@ti.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.