From: Artem Bityutskiy <dedekind1@gmail.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Li Yang-R58472 <r58472@freescale.com>,
"linuxppc-dev@lists.ozlabs.org list"
<linuxppc-dev@lists.ozlabs.org>,
"b35362@freescale.com>" <b35362@freescale.com>,
"linux-kernel@vger.kernel.org Kernel"
<linux-kernel@vger.kernel.org>,
linux-mtd@lists.infradead.org,
Scott Wood <scottwood@freescale.com>,
Andrew Morton <akpm@linux-foundation.org>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH v2] Integrated Flash Controller support
Date: Wed, 30 Nov 2011 10:51:12 +0200 [thread overview]
Message-ID: <1322643080.24797.413.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <EFF451D9-552A-4820-90D3-BF3156D5B25F@kernel.crashing.org>
[-- Attachment #1: Type: text/plain, Size: 404 bytes --]
On Tue, 2011-11-29 at 19:47 -0600, Kumar Gala wrote:
> As Scott said, I was more asking about the 2nd patch in the sequence
> which did touch MTD. Since that one is dependent on this patch,
> wondering how we wanted to handle them.
I do not have time to review it, but it looks OK, so I'd suggest to
merge it vie the same tree as the rest of the patches.
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-11-30 8:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-31 9:38 [PATCH v2] Integrated Flash Controller support b35362
2011-10-31 9:38 ` [PATCH] mtd/nand : set Nand flash page address to FBAR and FPAR correctly b35362
2011-10-31 9:38 ` [PATCH 2/2] NAND Machine support for Integrated Flash Controller b35362
2011-11-23 3:41 ` [PATCH v2] Integrated Flash Controller support Kumar Gala
2011-11-24 14:24 ` Kumar Gala
2011-11-29 21:40 ` Artem Bityutskiy
2011-11-29 21:48 ` Scott Wood
2011-11-30 1:47 ` Kumar Gala
2011-11-30 8:51 ` Artem Bityutskiy [this message]
2011-12-14 11:13 ` Li Yang-R58472
2011-12-17 16:40 ` Artem Bityutskiy
2011-11-29 21:36 ` 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=1322643080.24797.413.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=b35362@freescale.com \
--cc=dwmw2@infradead.org \
--cc=galak@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=r58472@freescale.com \
--cc=scottwood@freescale.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).