From: Artem Bityutskiy <dedekind1@gmail.com>
To: Scott Branden <sbranden@broadcom.com>
Cc: Artem Bityutskiy <dedekind@infradead.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"linux-arm-kernel@lists.arm.linux.org.uk"
<linux-arm-kernel@lists.arm.linux.org.uk>,
"Leo \(Hao\) Chen" <leochen@broadcom.com>
Subject: Re: [PATCH v3 26/27] [ARM] [NAND] [bcmring] add bcmring umi nand driver support
Date: Sun, 09 Aug 2009 10:27:21 +0300 [thread overview]
Message-ID: <4A7E7A59.3080501@gmail.com> (raw)
In-Reply-To: <9383297B60843144AC17878B479520F1109ECFC740@SJEXCHCCR01.corp.ad.broadcom.com>
On 08/09/2009 10:12 AM, Scott Branden wrote:
> Hi Artem,
>
> Thanks for the comments.
>
> This particular code (nand_bcm_umi.h) is shared between multiple
> OS's, simulation environments, and non-OS's. As you are aware, this
> alone presents maintenance challenges. The simplest approach was to
> make an include file and wrap that for each particular environment.
> We will look at splitting this into a C and H file.
Well, the idea is that include/linux/mtd the external MTD interface,
so you should put only the stuff which is about MTD<->other subsystems.
There are also headers that are about MTD core <-> MTD drivers interface.
So if you need to share something between different parts of your driver,
this should be rather in drivers/mtd/nand/, not in include/linux/mtd.
> The file passes Linux's checkpatch scripts. I don't see a need for
> any further requirement? It would be sad if a particular linux
> maintainer was stuck on other stylistic concerns because other
> maintainers are not. Especially when this code is not specifically
> written for linux and is supported, tested, and maintained by us.
I do not have a strong opinion here, and I'm personally fine with this.
I mean, I do not mind if you ignore my /**...**/ and 'WindowsStyleVars'
comment.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2009-08-09 7:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-17 19:13 [PATCH v3 26/27] [ARM] [NAND] [bcmring] add bcmring umi nand driver support Leo (Hao) Chen
2009-07-19 5:08 ` Artem Bityutskiy
2009-07-19 10:56 ` Steve Chen
2009-07-21 22:46 ` Leo (Hao) Chen
2009-07-22 6:12 ` Artem Bityutskiy
2009-07-28 22:08 ` Leo (Hao) Chen
2009-07-28 22:38 ` Leo (Hao) Chen
2009-08-09 5:16 ` Artem Bityutskiy
2009-08-09 7:12 ` Scott Branden
2009-08-09 7:27 ` Artem Bityutskiy [this message]
2009-08-10 17:33 ` 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=4A7E7A59.3080501@gmail.com \
--to=dedekind1@gmail.com \
--cc=dedekind@infradead.org \
--cc=leochen@broadcom.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-mtd@lists.infradead.org \
--cc=sbranden@broadcom.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.