From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] spl: Make CONFIG_SPL_BUILD contain more functionality
Date: Fri, 17 May 2013 11:39:16 -0500 [thread overview]
Message-ID: <1368808756.8202.53@snotra> (raw)
In-Reply-To: <B3A295C5BD5B13458B2F5C6AFAD910466F3059@039-SN2MPN1-022.039d.mgd.msft.net> (from B40530@freescale.com on Fri May 17 10:04:12 2013)
On 05/17/2013 10:04:12 AM, Zhang Ying-B40530 wrote:
>
> ________________________________________
> From: Tom Rini [tom.rini at gmail.com] on behalf of Tom Rini
> [trini at ti.com]
> Sent: Friday, May 17, 2013 2:54 PM
> To: Zhang Ying-B40530
> Cc: Xie at theia.denx.de; u-boot at lists.denx.de; afleming at gmail.com;
> Wood at theia.denx.de; Wood Scott-B07421
> Subject: Re: [U-Boot] [PATCH v2] spl: Make CONFIG_SPL_BUILD contain
> more functionality
>
> On Fri, May 17, 2013 at 02:26:04PM +0000, Zhang Ying-B40530 wrote:
> > [Zhang Ying]
> > So for this patch, are there any problem?
> >
>
> Yes. It doesn't seem to do anything. Which is why I want to see the
> series of patches that result in new functionality on some boards, so
> we
> can evaluate the changes in context.
> [Zhang Ying]
> It seems to be several patches were sent together.
No, they weren't. They were sent separately. Use git format-patch to
generate all the patches at once, so they're numbered, and use git
send-email to send them all at once, so they're threaded properly.
-Scott
next prev parent reply other threads:[~2013-05-17 16:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 9:12 [U-Boot] [PATCH v2] spl: Make CONFIG_SPL_BUILD contain more functionality ying.zhang at freescale.com
2013-05-17 12:34 ` Tom Rini
2013-05-17 14:10 ` Zhang Ying-B40530
2013-05-17 14:20 ` Tom Rini
2013-05-17 14:26 ` Zhang Ying-B40530
2013-05-17 14:54 ` Tom Rini
2013-05-17 15:04 ` Zhang Ying-B40530
2013-05-17 16:39 ` Scott Wood [this message]
2013-05-17 16:41 ` Zhang Ying-B40530
2013-05-24 19:06 ` Scott Wood
2013-05-24 19:16 ` Tom Rini
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=1368808756.8202.53@snotra \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.