From: Alessandro Rubini <rubini-list@gnudd.com>
To: vimal.newwork@gmail.com
Cc: STEricsson_nomadik_linux@list.st.com,
linux-mtd@lists.infradead.org, rubini-list@gnudd.com,
linux@arm.linux.org.uk, andrea.gallo@stericsson.com
Subject: Re: [PATCH V5 1/2] Nand driver for Nomadik 8815 SoC (on NHK8815 board)
Date: Fri, 24 Jul 2009 14:37:51 +0200 [thread overview]
Message-ID: <20090724123750.GA25563@mail.gnudd.com> (raw)
In-Reply-To: <ce9ab5790907240510y752885b9m2debac82bbdd7401@mail.gmail.com>
> Please run ''checkpatch.pl' for this patch and try to fix the errors.
Ok, will do. Although I don't agree with everything checkpatch is
saying (I've heard checkpatch is meant as suggestions, to be
considered but not applied blindly, so I behaved accordingly).
> this can be 'NAND_ECC_SOFT' here... then
As explained in the comments above, there is the hardware in there,
only I've not been able to use it yet. So I prefer to stay HW and then
change as little as possible. But, unless you confirm I can do that,
I'll write SOFT in there as requested.
Will repost on monday, I'm off for the weekend.
/alessandro
next prev parent reply other threads:[~2009-07-24 12:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-24 11:29 [PATCH V5 0/2] Nand and OneNand for ARM Nomadik Alessandro Rubini
2009-07-24 11:30 ` [PATCH V5 2/2] OneNand support for Nomadik 8815 SoC (on NHK8815 board) Alessandro Rubini
2009-07-24 11:30 ` Alessandro Rubini
2009-07-24 11:32 ` [PATCH V5 1/2] Nand driver " Alessandro Rubini
2009-07-24 11:32 ` Alessandro Rubini
[not found] ` <50ed4996479c95b93714ac814608d5f0db85238d.1248434636.git.rubini@unipv.it>
2009-07-24 12:10 ` vimal singh
2009-07-24 12:37 ` Alessandro Rubini [this message]
2009-07-27 6:28 ` vimal singh
2009-07-27 8:46 ` vimal singh
2009-08-09 6:43 ` Artem Bityutskiy
2009-08-09 7:03 ` Alessandro Rubini
2009-08-09 7:17 ` Artem Bityutskiy
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=20090724123750.GA25563@mail.gnudd.com \
--to=rubini-list@gnudd.com \
--cc=STEricsson_nomadik_linux@list.st.com \
--cc=andrea.gallo@stericsson.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
--cc=vimal.newwork@gmail.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 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).