From: Nick Thompson <nick.thompson@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 1/1] TI: Davinci: NAND Driver Cleanup
Date: Wed, 17 Mar 2010 11:10:59 +0000 [thread overview]
Message-ID: <4BA0B8C3.7060909@ge.com> (raw)
In-Reply-To: <1268765506-9957-1-git-send-email-cyril@ti.com>
On 16/03/10 18:51, Cyril Chemparathy wrote:
> #define davinci_emif_regs \
> - ((struct davinci_emif_regs *)DAVINCI_ASYNC_EMIF_CNTRL_BASE)
> + ((struct davinci_emif_regs *)DAVINCI_ASYNC_EMIF_CNTRL_BASE)
> +
I didn't check, but I would assume checkpatch would complain about the
spaces that have crept in here? Can you please restore the original tab?
Mainly this would remove these lines from your patch, which cause a
small confusion as to what exactly has changed and why.
If you haven't already done so, it would be a good idea to run
checkpatch to check for any other formatting violations.
Other than that, the patch looks good to me.
Thanks,
Nick.
next prev parent reply other threads:[~2010-03-17 11:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-16 18:51 [U-Boot] [PATCH v2 1/1] TI: Davinci: NAND Driver Cleanup Cyril Chemparathy
2010-03-17 11:10 ` Nick Thompson [this message]
2010-03-17 14:04 ` Chemparathy, Cyril
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=4BA0B8C3.7060909@ge.com \
--to=nick.thompson@ge.com \
--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