From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] MTD update
Date: Thu, 8 Nov 2007 14:31:30 +0100 [thread overview]
Message-ID: <200711081431.31194.sr@denx.de> (raw)
In-Reply-To: <2563ac9e0711070614y1a7032e6y351c9b8da1197fa@mail.gmail.com>
Hi William,
On Wednesday 07 November 2007, William Juul wrote:
> > We don't have YAFFS support in U-Boot ???
>
> My intent is to submit a patch for this as well. A YAFFS patch will
> build on this patch but is logically distinct so I kept it out for now
> as this patch is more than large enough as it is.
Good.
> > > We have set up a git repository were you can pull the patch:
> > > http://git.tandberg.com/tandberg/u-boot.git
> >
> > This is nice, but it is nevertheless mandatory to post the patches
> > here on the list for review.
>
> As I mentioned in my previous post, some of the changes are very big
> and will not fit under the size-limit unless I split single-file
> patches. Stefan Roese kindly suggested that we could set up a git
> server and put the changes there. I can of-course send all the small
> file-patches to the mailing-list and keep the big changes on the git
> server, but since this logically is all one big patch I thought it
> would be better to keep the whole change together on the git-server.
>
> As I see it, the patch can be reviewed from the git-server and
> comments/snippets can be discussed on the mailing-list. Further, as
> partly stated in my post, I consider this to be work in progress, but
> I need help from the community to finish this off. I would then think
> that I (or the maintainer, if he prefers to run this from a branch in
> his git-tree) can incorporate comments and that the maintainer can
> pull this into his tree when/if he and the community feels that this
> is mature enough.
I think it will be best, that I add this new NAND driver code into a branch of
the u-boot-nand-flash custodian repository. But only after the first issues
are solved. For example I found quite a lot of coding style issues in your
patch:
- Leading white spaces
- Trailing white spaces
- Indentation seems to be sometimes with 4 spaces instead of using a tab
- C++ comments (//)
Please clean this up. I'll send a more detailed review soon.
Thanks.
Best regards,
Stefan
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
next prev parent reply other threads:[~2007-11-08 13:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 11:29 [U-Boot-Users] [PATCH] MTD update William Juul
2007-11-07 13:30 ` Wolfgang Denk
2007-11-07 14:14 ` William Juul
2007-11-07 19:46 ` Wolfgang Denk
2007-11-08 13:05 ` Stefan Roese
2007-11-08 13:31 ` Stefan Roese [this message]
2007-11-08 19:24 ` Wolfgang Denk
2007-11-09 9:12 ` William Juul
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=200711081431.31194.sr@denx.de \
--to=sr@denx.de \
--cc=u-boot@lists.denx.de \
/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