From: David Woodhouse <dwmw2@infradead.org>
To: "Leo (Hao) Chen" <leochen@broadcom.com>
Cc: Linux MTD <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH] [MTD] bcmring: mtd nand driver
Date: Mon, 28 Sep 2009 15:37:10 -0700 [thread overview]
Message-ID: <1254177430.3034.790.camel@macbook.infradead.org> (raw)
In-Reply-To: <20090928222451.GF30661@broadcom.com>
On Mon, 2009-09-28 at 15:24 -0700, Leo (Hao) Chen wrote:
>
> I've updated the patch of mtd nand driver support for bcmring arch.
> It's now applicable to the latest kernel git tree (Linux 2.6.32-rc1).
>
> Please merge this patch into upstream.
> If further modification needed, let me know.
Thank you. On closer inspection, this patch is actually a whole lot
saner than it appears at first glance. The amount of superfluous
commenting made it look bad, when I first looked.
For example, a function called 'nand_dma_write' does _not_ need a
five-line comment block explaining that it 'Performs a write via DMA'.
Other comments, on a brief re-reading...
You're using a platform device, but you still hard-code the I/O address
you ioremap for bcm_imi_io_base -- is it possible for you to fix that,
and encode it in the platform device instead?
Also, do you need the USE_DMA and USE_HWECC macros? If they're always
enabled, can we lose some ifdefs?
Finally, can you convince me that this isn't an "additional restriction"
as prohibited by the GPL? :
+* Notwithstanding the above, under no circumstances may you combine this
+* software in any way with any other Broadcom software provided under a
+* license other than the GPL, without Broadcom's express prior written
+* consent.
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
next prev parent reply other threads:[~2009-09-28 22:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-28 22:24 [PATCH] [MTD] bcmring: mtd nand driver Leo (Hao) Chen
2009-09-28 22:37 ` David Woodhouse [this message]
2009-09-28 23:27 ` Leo (Hao) Chen
2009-09-30 0:02 ` Leo (Hao) Chen
2009-09-30 0:22 ` Scott Branden
2009-09-30 0:41 ` Leo (Hao) Chen
2009-09-30 17:25 ` Scott Branden
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=1254177430.3034.790.camel@macbook.infradead.org \
--to=dwmw2@infradead.org \
--cc=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