From: Yunpeng Gao <yunpeng.gao@intel.com>
To: Greg KH <gregkh@suse.de>
Cc: David Woodhouse <dwmw2@infradead.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2]Intel Moorestown NAND driver patch for mainline
Date: Tue, 9 Jun 2009 18:48:53 +0800 [thread overview]
Message-ID: <20090609104853.GA3046@intel.com> (raw)
In-Reply-To: <20090609003839.GB22766@suse.de>
On Tue, Jun 09, 2009 at 08:38:39AM +0800, Greg KH wrote:
> On Mon, Jun 08, 2009 at 11:47:10AM +0100, David Woodhouse wrote:
> > On Mon, 2009-06-08 at 12:23 +0800, Gao, Yunpeng wrote:
> > > The Moorestown NAND flash driver is licensed from the Moorestown NAND
> > > controller vendor. It's a standalone NAND driver. According to the
> > > vendor, this driver has some advanced features specific to the
> > > controller hardware and is difficult to port to MTD subsystem.
> >
> > I don't believe it. If the MTD subsystem doesn't support certain
> > features, the MTD subsystem needs to be updated to cope.
>
> Based on this response, I am guessing that you do not want me to take
> this in the staging tree? :)
>
> If so, please let me know and I'll drop it.
>
> thanks,
>
> greg k-h
Hi Greg,
Thanks for the reminder. But I need to discuss with David first to get more
info from him and then decide to submit to MTD or not. Before that, please
hold this patch in staging tree and don't drop it. Thank you.
Rgds,
Yunpeng
next prev parent reply other threads:[~2009-06-09 3:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-06 16:44 [PATCH 1/2]Intel Moorestown NAND driver patch for mainline Yunpeng Gao
2009-06-06 11:11 ` Jiri Slaby
2009-06-06 14:57 ` Greg KH
2009-06-08 3:34 ` Gao, Yunpeng
2009-06-08 3:08 ` Gao, Yunpeng
2009-06-06 15:04 ` Alan Cox
2009-06-08 4:23 ` Gao, Yunpeng
2009-06-08 10:47 ` David Woodhouse
2009-06-09 0:38 ` Greg KH
2009-06-09 10:48 ` Yunpeng Gao [this message]
2009-06-23 10:59 ` Gao, Yunpeng
2009-06-23 11:05 ` David Woodhouse
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=20090609104853.GA3046@intel.com \
--to=yunpeng.gao@intel.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dwmw2@infradead.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox