From: Ben Dooks <ben-linux@fluff.org>
To: christian pellegrin <chripell@gmail.com>
Cc: Ben Dooks <ben-linux@fluff.org>,
linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: approaching last call for updatyes
Date: Mon, 17 May 2010 06:00:38 +0100 [thread overview]
Message-ID: <20100517050038.GU26401@trinity.fluff.org> (raw)
In-Reply-To: <AANLkTimHifdCStUZJ_Xgyf2n5mA47Jdj2zscWNB13LDq@mail.gmail.com>
On Thu, May 13, 2010 at 11:37:30AM +0200, christian pellegrin wrote:
> The fix for NAND clock stop on idle is missing. Without it I suggest
> to mark the option CONFIG_MTD_NAND_S3C2410_CLKSTOP broken.
this is something for the relevant mtd maintainer to merge.
--
Ben
Q: What's a light-year?
A: One-third less calories than a regular year.
WARNING: multiple messages have this Message-ID (diff)
From: ben-linux@fluff.org (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: approaching last call for updatyes
Date: Mon, 17 May 2010 06:00:38 +0100 [thread overview]
Message-ID: <20100517050038.GU26401@trinity.fluff.org> (raw)
In-Reply-To: <AANLkTimHifdCStUZJ_Xgyf2n5mA47Jdj2zscWNB13LDq@mail.gmail.com>
On Thu, May 13, 2010 at 11:37:30AM +0200, christian pellegrin wrote:
> The fix for NAND clock stop on idle is missing. Without it I suggest
> to mark the option CONFIG_MTD_NAND_S3C2410_CLKSTOP broken.
this is something for the relevant mtd maintainer to merge.
--
Ben
Q: What's a light-year?
A: One-third less calories than a regular year.
next prev parent reply other threads:[~2010-05-17 5:00 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
2010-05-13 10:44 ` Vasily Khoruzhick
2010-05-17 5:00 ` Ben Dooks [this message]
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=20100517050038.GU26401@trinity.fluff.org \
--to=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.