From: Vasily Khoruzhick <anarsoul@gmail.com>
To: linux-arm-kernel@lists.infradead.org
Cc: christian pellegrin <chripell@gmail.com>,
Ben Dooks <ben-linux@fluff.org>,
linux-samsung-soc@vger.kernel.org
Subject: Re: approaching last call for updatyes
Date: Thu, 13 May 2010 13:44:02 +0300 [thread overview]
Message-ID: <201005131344.13949.anarsoul@gmail.com> (raw)
In-Reply-To: <AANLkTimHifdCStUZJ_Xgyf2n5mA47Jdj2zscWNB13LDq@mail.gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 376 bytes --]
В сообщении от 13 мая 2010 12:37:30 автор christian pellegrin написал:
> The fix for NAND clock stop on idle is missing. Without it I suggest
> to mark the option CONFIG_MTD_NAND_S3C2410_CLKSTOP broken.
Confirmed, CLKSTOP option is not working on my rx1950, I'm not able to
read NAND after resume from suspend with CLKSTOP enabled.
Regards
Vasily
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: anarsoul@gmail.com (Vasily Khoruzhick)
To: linux-arm-kernel@lists.infradead.org
Subject: approaching last call for updatyes
Date: Thu, 13 May 2010 13:44:02 +0300 [thread overview]
Message-ID: <201005131344.13949.anarsoul@gmail.com> (raw)
In-Reply-To: <AANLkTimHifdCStUZJ_Xgyf2n5mA47Jdj2zscWNB13LDq@mail.gmail.com>
? ????????? ?? 13 ??? 2010 12:37:30 ????? christian pellegrin ???????:
> The fix for NAND clock stop on idle is missing. Without it I suggest
> to mark the option CONFIG_MTD_NAND_S3C2410_CLKSTOP broken.
Confirmed, CLKSTOP option is not working on my rx1950, I'm not able to
read NAND after resume from suspend with CLKSTOP enabled.
Regards
Vasily
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20100513/50f91ff0/attachment.sig>
next prev parent reply other threads:[~2010-05-13 10:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 9:15 approaching last call for updatyes Ben Dooks
2010-05-13 9:15 ` Ben Dooks
2010-05-13 9:20 ` Vasily Khoruzhick
2010-05-13 9:20 ` Vasily Khoruzhick
2010-05-13 9:37 ` christian pellegrin
2010-05-13 9:37 ` christian pellegrin
2010-05-13 10:44 ` Vasily Khoruzhick [this message]
2010-05-13 10:44 ` Vasily Khoruzhick
2010-05-17 5:00 ` Ben Dooks
2010-05-17 5:00 ` Ben Dooks
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=201005131344.13949.anarsoul@gmail.com \
--to=anarsoul@gmail.com \
--cc=ben-linux@fluff.org \
--cc=chripell@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@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.