From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Pad data length for nand write
Date: Tue, 17 Feb 2009 12:41:08 -0600 [thread overview]
Message-ID: <499B04C4.7080904@freescale.com> (raw)
In-Reply-To: <499B03FD.7050207@siconix.com>
Derek Ou wrote:
> Sorry that my patch went out twice. I ran into smtp authentication issue
> with git-send-email. Also, what is the right way to add more comments
> to a patch? Should I edit the patch generated by git-format-patch or I
> should just add commit title, blank line and the full commit message when
> I git commit my change locally.
The latter, for anything that belongs in the permanent commit message.
For transient information such as what changed since the previous
version of the patch, edit the resulting patch below the "---".
-Scott
next prev parent reply other threads:[~2009-02-17 18:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 17:15 [U-Boot] [PATCH] Pad data length for nand write Derek Ou
2009-02-17 17:15 ` Derek Ou
2009-02-17 18:51 ` Scott Wood
2009-02-17 20:54 ` Derek Ou
2009-02-17 21:16 ` Scott Wood
2009-02-17 21:37 ` Derek Ou
2009-02-17 17:55 ` Mike Frysinger
2009-02-17 18:37 ` Derek Ou
2009-02-17 18:41 ` Scott Wood [this message]
2009-02-17 20:22 ` Wolfgang Denk
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=499B04C4.7080904@freescale.com \
--to=scottwood@freescale.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