From: "Leo (Hao) Chen" <leochen@broadcom.com>
To: "Artem Bityutskiy" <dedekind1@gmail.com>, dwmw2@infradead.org
Cc: Linux MTD <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH v5] [MTD] BCMRING: mtd nand umi driver support
Date: Fri, 28 Aug 2009 11:43:29 -0700 [thread overview]
Message-ID: <20090828184329.GD20707@broadcom.com> (raw)
In-Reply-To: <1251436582.3514.7.camel@localhost>
Got it. Thanks.
David, would you please include my mtd driver patch in your tree? Our other 23
patches for bcmring support in arch/arm are wating for this patch, so
that we can get the defconfig build in linux-next. Let me know if
there is any improvement needed. Thanks a lot.
Br,
Leo
On Thu, Aug 27, 2009 at 10:16:22PM -0700, Artem Bityutskiy wrote:
> On Thu, 2009-08-27 at 11:35 -0700, Leo (Hao) Chen wrote:
> > 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?
> >
>
> You should bug David Woodhouse. I've added your driver to my l2-mtd-2.6
> tree, so he should take a look at it at some point:
> http://git.infradead.org/users/dedekind/l2-mtd-2.6.git/commit/eef42e4b8b0de71f3fdac4577c0eea0537ce0386
>
> --
> Best Regards,
> Artem Bityutskiy (Артём Битюцкий)
>
>
--
Leo Hao Chen
Software Engineer
Broadcom Canada Inc.
prev parent reply other threads:[~2009-08-28 18:43 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
2009-08-28 5:16 ` Artem Bityutskiy
2009-08-28 18:43 ` Leo (Hao) Chen [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=20090828184329.GD20707@broadcom.com \
--to=leochen@broadcom.com \
--cc=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--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