From: "Leo (Hao) Chen" <leochen@broadcom.com>
To: "Linux MTD" <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH v5] [MTD] BCMRING: mtd nand umi driver support
Date: Thu, 27 Aug 2009 11:35:58 -0700 [thread overview]
Message-ID: <20090827183558.GB4222@broadcom.com> (raw)
In-Reply-To: <20090821221701.GF14815@broadcom.com>
Hi,
As our bcmring code have been merged by Russell into linux-next repo, we really
need this mtd driver be merged into the kenrel as well to get a
working system.
So, I just want to know if our patch for bcmring mtd driver is accepted or not.
If not, what shall we improve? If yes, when can we get our code into linux-next repos?
Or we have to submit the patch to any tracking system?
Thanks for your advice.
best,
Leo
On Fri, Aug 21, 2009 at 03:17:01PM -0700, Leo (Hao) Chen wrote:
> Hi,
>
> I'd submit the latest version of our patch to support mtd nand driver
> for bcmring arch. This patch is against the latest git tree and
> passed the checkpatch.pl script. The patch set of bcmring arch. support
> has been accepted by Russell in linux-arm-kernel. Russell told me
> that the mtd nand driver support of bcmring should go through the linux-mtd list.
> So, I submit my mtd nand driver patch here again.
> Thanks for all the review comments before.
> I've fixed all the bugs, coding style errors/warnings and split the inline functions
> into separate C file.
>
> Please review it again and let us know if there is any other problem.
> If it is okay, can this patch be accepted?
>
> Thanks,
>
> Leo
>
next prev parent reply other threads:[~2009-08-27 18:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-21 22:17 [PATCH v5] [MTD] BCMRING: mtd nand umi driver support Leo (Hao) Chen
2009-08-27 18:35 ` Leo (Hao) Chen [this message]
2009-08-28 5:16 ` Artem Bityutskiy
2009-08-28 18:43 ` Leo (Hao) Chen
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=20090827183558.GB4222@broadcom.com \
--to=leochen@broadcom.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