From: "Andreas Bießmann" <andreas.devel@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [V3] arm: Fix to mistake clean the memory space
Date: Mon, 09 Jul 2012 13:21:12 +0200 [thread overview]
Message-ID: <4FFABEA8.6000500@gmail.com> (raw)
In-Reply-To: <4FF8374E.6020804@gmail.com>
Dear Zhong Hongbo,
On 07.07.2012 15:19, Zhong Hongbo wrote:
> On 07/07/2012 05:58 PM, Albert ARIBAUD wrote:
>> Hi Zhong Hongbo,
>>
>> On Sat, 7 Jul 2012 17:47:16 +0800, Zhong Hongbo <bocui107@gmail.com> wrote:
>>> From: Zhong Hongbo <bocui107@gmail.com>
>> Almost there... The PATCH part is missing, i.e. you should not tag "[V3]"
>> but "[PATCH V3]".
>
> Ok,
well, you sent v4 but didn't respect this comment. Please read
http://www.denx.de/wiki/view/U-Boot/Patches#Sending_updated_patch_versions
especially this part:
---8<---
Make an appropriate note that this is a re-submission in the subject
line, eg. "[PATCH v2] Add support for feature X". git format-patch
--subject-prefix="PATCH v2" can be used in this case.
--->8---
Another option is to use 'git send-email --annotate ...' and change the
subject line.
>> Just to make sure patchwork gets it right, please repost a V4 of this
>> properly tagged with "[PATCH V4]".
I think patchwork got it right http://patchwork.ozlabs.org/patch/169595/
and http://patchwork.ozlabs.org/patch/169572/. So I would say you do not
need to resend a v5 of the same patch cause of this formal 'fault'.
Albert, do you have the same opinion?
Albert, I think we should count this a fix and pull into this upcoming
release. How do you think about?
Best regards
Andreas Bie?mann
next prev parent reply other threads:[~2012-07-09 11:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-07 9:47 [U-Boot] [V3] arm: Fix to mistake clean the memory space Zhong Hongbo
2012-07-07 9:58 ` Albert ARIBAUD
2012-07-07 13:19 ` Zhong Hongbo
2012-07-09 11:21 ` Andreas Bießmann [this message]
2012-07-09 14:20 ` Albert ARIBAUD
2012-07-12 9:35 ` Andreas Bießmann
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=4FFABEA8.6000500@gmail.com \
--to=andreas.devel@googlemail.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.