From: Artem Bityutskiy <dedekind1@gmail.com>
To: "Enric Balletbò i Serra" <eballetbo@gmail.com>
Cc: linux-mtd@lists.infradead.org, linux-omap@vger.kernel.org,
Kyungmin Park <kmpark@infradead.org>
Subject: Re: Possible bug in onenand_base ?
Date: Thu, 08 Jul 2010 12:58:07 +0300 [thread overview]
Message-ID: <1278583087.20321.0.camel@localhost> (raw)
In-Reply-To: <AANLkTin43tv-AiFjwNkUE7ijy_ADMtsZTrqo_PY3DpCE@mail.gmail.com>
On Thu, 2010-07-08 at 11:55 +0200, Enric Balletbò i Serra wrote:
> Hello,
>
> I made new tests regarding this issue. Looks like the problem is
> reading from the OneNAND device.
Did you try older kernel and then bisecting who is responsible for the
breakage?
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
WARNING: multiple messages have this Message-ID (diff)
From: Artem Bityutskiy <dedekind1@gmail.com>
To: "Enric Balletbò i Serra" <eballetbo@gmail.com>
Cc: Kyungmin Park <kmpark@infradead.org>,
linux-omap@vger.kernel.org, linux-mtd@lists.infradead.org
Subject: Re: Possible bug in onenand_base ?
Date: Thu, 08 Jul 2010 12:58:07 +0300 [thread overview]
Message-ID: <1278583087.20321.0.camel@localhost> (raw)
In-Reply-To: <AANLkTin43tv-AiFjwNkUE7ijy_ADMtsZTrqo_PY3DpCE@mail.gmail.com>
On Thu, 2010-07-08 at 11:55 +0200, Enric Balletbò i Serra wrote:
> Hello,
>
> I made new tests regarding this issue. Looks like the problem is
> reading from the OneNAND device.
Did you try older kernel and then bisecting who is responsible for the
breakage?
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-07-08 9:58 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-30 10:05 Possible bug in onenand_base ? Enric Balletbò i Serra
2010-04-30 10:05 ` Enric Balletbò i Serra
2010-05-05 5:56 ` Artem Bityutskiy
2010-05-05 5:56 ` Artem Bityutskiy
2010-05-06 3:46 ` Kyungmin Park
2010-05-06 3:46 ` Kyungmin Park
2010-05-06 11:22 ` Enric Balletbò i Serra
2010-05-06 11:22 ` Enric Balletbò i Serra
2010-05-06 11:44 ` Kyungmin Park
2010-05-06 11:44 ` Kyungmin Park
2010-05-06 13:02 ` Enric Balletbò i Serra
2010-05-06 13:02 ` Enric Balletbò i Serra
2010-05-12 10:29 ` Enric Balletbò i Serra
2010-05-12 10:29 ` Enric Balletbò i Serra
2010-05-12 13:16 ` Enric Balletbò i Serra
2010-05-12 13:16 ` Enric Balletbò i Serra
2010-07-08 9:55 ` Enric Balletbò i Serra
2010-07-08 9:55 ` Enric Balletbò i Serra
2010-07-08 9:58 ` Artem Bityutskiy [this message]
2010-07-08 9:58 ` Artem Bityutskiy
2010-07-08 10:11 ` Enric Balletbò i Serra
2010-07-08 10:11 ` Enric Balletbò i Serra
2010-07-08 10:22 ` Artem Bityutskiy
2010-07-08 10:22 ` Artem Bityutskiy
2010-07-12 14:59 ` Enric Balletbò i Serra
2010-07-12 14:59 ` Enric Balletbò i Serra
-- strict thread matches above, loose matches on Subject: below --
2010-07-14 8:52 ROHIT H.S
2010-07-14 14:37 ` Enric Balletbò i Serra
2010-07-15 9:25 ` Rohit Hassan Sathyanarayan
2010-07-15 11:19 ` Enric Balletbò i Serra
2010-07-16 12:04 ` Rohit Hassan Sathyanarayan
2010-07-18 16:47 ` 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=1278583087.20321.0.camel@localhost \
--to=dedekind1@gmail.com \
--cc=eballetbo@gmail.com \
--cc=kmpark@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.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.