From: Sean MacLennan <smaclennan@pikatech.com>
To: "Josh Boyer" <jwboyer@linux.vnet.ibm.com>,
<linux-mtd@lists.infradead.org>, <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] ndfc driver
Date: Thu, 4 Dec 2008 12:17:01 -0500 [thread overview]
Message-ID: <20081204121701.5ef90226@lappy.seanm.ca> (raw)
In-Reply-To: <20081204090107.20269571@zod.rchland.ibm.com>
On Thu, 4 Dec 2008 09:01:07 -0500
"Josh Boyer" <jwboyer@linux.vnet.ibm.com> wrote:
> On Wed, 3 Dec 2008 22:28:32 -0500
> Sean MacLennan <smaclennan@pikatech.com> wrote:
>
> Hi Sean,
>
> A couple of comments/requests below.
>
> In addition to an example DTS patch (probably to warp itself), could
> you briefly write up a binding and put it in
> Documentation/powerpc/dts-bindings/amcc (or similar)? Also please CC
> the devicetree-discuss list on that part.
The DTS patch was a separate email to the linuxppc-dev list. I'll try to
find it.
I will look into writing up the binding.
> Looking over the patch it seems pretty straight-forward and I don't
> see anything immediately wrong with it. You do have a number of
> semi-unrelated changes to the actual port to of_platform though, like
> the s/__raw_writel/out_be32 stuff, the addition of partition parsing,
> etc. I'm wondering if you could do those fixups separately from the
> actual port.
>
> Also, could you document why the data structures changed as they did
> in the changelog or perhaps in a summary email.
The __raw_writel changes where from feedback from this list. I will try
to find the email.
This patch originally goes back to January... so I have problems
remembering why all the changes where made ;) Believe it or not, we
have gone through 3 or 4 repositories since then. Finding history is
basically impossible :( So I have to try to rely on an email trail.
> You also seem to only support a single NAND chip, however the NDFC can
> support multiple chips. Have you looked at how the the fsl_elbc_nand
> driver does multiple chip support? If not, could you at least
> document the limitation in the patch?
I will document the limitation. I do not have access to a board with
multiple chips and I don't like submitting something I can't test.
Cheers,
Sean
next prev parent reply other threads:[~2008-12-04 17:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20081203222832.3fc77d28@lappy.seanm.ca>
2008-12-04 14:01 ` [PATCH] ndfc driver Josh Boyer
2008-12-04 17:17 ` Sean MacLennan [this message]
2008-12-09 0:34 ` Sean MacLennan
2008-12-09 2:11 ` Anton Vorontsov
2008-12-09 2:45 ` Sean MacLennan
2008-12-09 3:32 ` Josh Boyer
2008-12-09 4:54 ` Sean MacLennan
2008-12-09 7:57 ` Mitch Bradley
2008-12-10 4:01 ` Sean MacLennan
2008-12-10 8:28 ` Mitch Bradley
2008-12-09 6:10 ` Stefan Roese
2008-12-09 11:24 ` Josh Boyer
2008-12-10 23:16 ` Sean MacLennan
2008-12-17 4:14 ` Sean MacLennan
2008-12-17 11:34 ` Josh Boyer
2008-12-17 13:26 ` Josh Boyer
2008-12-09 0:51 ` Sean MacLennan
[not found] <9293074.419171225391386417.JavaMail.nabble@isper.nabble.com>
[not found] ` <20081030195858.28900ee5@lappy.seanm.ca>
[not found] ` <490D68A8.4060905@embedded-sol.com>
[not found] ` <20081102124804.15003002@lappy.seanm.ca>
[not found] ` <490E02D7.5050402@embedded-sol.com>
[not found] ` <20081102145811.6da10ef4@lappy.seanm.ca>
[not found] ` <490E074F.5050909@embedded-sol.com>
[not found] ` <20081102152958.42e88283@lappy.seanm.ca>
[not found] ` <490E4D0D.9060207@embedded-sol.com>
[not found] ` <20081102204510.3d8e71f2@lappy.seanm.ca>
2008-11-03 10:56 ` Felix Radensky
2008-10-30 6:08 Sean MacLennan
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=20081204121701.5ef90226@lappy.seanm.ca \
--to=smaclennan@pikatech.com \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).