From: Artem Bityutskiy <dedekind1@gmail.com>
To: Kevin Hilman <khilman@deeprootsystems.com>
Cc: linux-mtd@lists.infradead.org,
davinci-linux-open-source@linux.davincidsp.com,
Sekhar Nori <nsekhar@ti.com>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH 0/6] davinci: add support for aemif timing configuration
Date: Tue, 31 Aug 2010 14:37:40 +0300 [thread overview]
Message-ID: <1283254660.2018.29.camel@brekeke> (raw)
In-Reply-To: <877hj8b20x.fsf@deeprootsystems.com>
On Mon, 2010-08-30 at 07:36 -0700, Kevin Hilman wrote:
> > Pushed to l2-mtd-2.6.git / dunno.
>
> Hi Artem,
>
> If it's OK with you, and with your Ack, I'd prefer to merge this series
> via the davinci tree.
>
> The reason is because the files touched in arch/arm/mach-davinci/* are
> also getting lots of other changes for 2.6.37, and I'd like to minimize
> conflicts.
Right, I've just removed them from my tree.
> Let me know if that's OK with you and if I can add your signoff to the
> drivers/mtd/* patches.
The MTD part is small there, feel free to add
Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
Thanks!
--
Best Regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2010-08-31 11:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-09 10:16 [PATCH 0/6] davinci: add support for aemif timing configuration Sekhar Nori
2010-08-09 10:16 ` [PATCH v3 1/6] " Sekhar Nori
2010-08-09 10:16 ` [PATCH v2 2/6] nand: davinci: add support for " Sekhar Nori
2010-08-09 10:16 ` [PATCH 3/6] davinci: dm644x evm: setup NAND flash timing Sekhar Nori
2010-08-09 10:16 ` [PATCH 4/6] davinci: am17x/da830/omap-l137 " Sekhar Nori
2010-08-09 10:16 ` [PATCH 5/6] davinci: am18x/da850/omap-l138 " Sekhar Nori
2010-08-09 10:16 ` [PATCH v2 6/6] davinci: dm6467t " Sekhar Nori
2010-08-29 11:48 ` [PATCH 0/6] davinci: add support for aemif timing configuration Artem Bityutskiy
2010-08-30 14:36 ` Kevin Hilman
2010-08-31 11:37 ` Artem Bityutskiy [this message]
2010-08-31 14:49 ` Kevin Hilman
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=1283254660.2018.29.camel@brekeke \
--to=dedekind1@gmail.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=dwmw2@infradead.org \
--cc=khilman@deeprootsystems.com \
--cc=linux-mtd@lists.infradead.org \
--cc=nsekhar@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).