From: Artem Bityutskiy <dedekind@infradead.org>
To: Kevin Hilman <khilman@deeprootsystems.com>
Cc: davinci-linux-open-source@linux.davincidsp.com,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH] NAND: davinci: update clock naming
Date: Sun, 31 May 2009 16:01:54 +0300 [thread overview]
Message-ID: <1243774914.11172.124.camel@localhost.localdomain> (raw)
In-Reply-To: <1243641862-1404-1-git-send-email-khilman@deeprootsystems.com>
On Fri, 2009-05-29 at 17:04 -0700, Kevin Hilman wrote:
> DaVinci clock support has been updated in mainline.
> Update clock names accordingly.
>
> Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
> ---
> drivers/mtd/nand/davinci_nand.c | 7 ++++---
> 1 files changed, 4 insertions(+), 3 deletions(-)
I've taken this to my l2-mtd-2.6.git. Will also ping dwmw2 about
2.6.30 merging of this patch.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
prev parent reply other threads:[~2009-05-31 13:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-30 0:04 [PATCH] NAND: davinci: update clock naming Kevin Hilman
2009-05-30 0:28 ` David Brownell
2009-06-06 15:32 ` David Woodhouse
2009-05-31 13:01 ` Artem Bityutskiy [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=1243774914.11172.124.camel@localhost.localdomain \
--to=dedekind@infradead.org \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-mtd@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox