From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Do not copy to same address
Date: Thu, 14 Apr 2011 08:28:18 +0200 [thread overview]
Message-ID: <4DA69402.1020403@aribaud.net> (raw)
In-Reply-To: <4DA403F3.2090304@arcor.de>
Hi Matthias,
Le 12/04/2011 09:49, Matthias Wei?er a ?crit :
> Well, as the patch is only slightly related to my original one I thought
> it is better to start a new patch as I had to change the subject also.
> The only relation between them would be the reference in the mail
> header. Maybe Wolfgang can bring some light into this situation.
>
> What would be the right way to post this patch?
Never mind with the previous patch, then; but please keep history of
this one (maybe including a patchwork URL pointing to the previous patch
with the other name) and tag its V2 in the subject line.
> And what would be the
> right way to post a patch doing exactly the same to the ARM optimized
> version of memcpy?
Simply submit a separate patch.
> Regards,
> Matthias
Amicalement,
--
Albert.
next prev parent reply other threads:[~2011-04-14 6:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 6:58 [U-Boot] [PATCH] Do not copy to same address Matthias Weisser
2011-04-12 7:05 ` Mike Frysinger
2011-04-12 7:16 ` Matthias Weißer
2011-04-12 7:06 ` Albert ARIBAUD
2011-04-12 7:13 ` Matthias Weißer
2011-04-12 7:27 ` Albert ARIBAUD
2011-04-12 7:49 ` Matthias Weißer
2011-04-14 6:28 ` Albert ARIBAUD [this message]
2011-05-23 9:03 ` [U-Boot] [PATCH V2] memcpy/memmove: " Matthias Weisser
2011-05-23 21:07 ` Alexander Holler
2011-05-23 21:55 ` Wolfgang Denk
2011-05-23 22:12 ` Alexander Holler
2011-05-23 22:22 ` Wolfgang Denk
2011-05-23 22:38 ` Alexander Holler
2011-05-24 3:47 ` Mike Frysinger
2011-05-24 13:03 ` Alexander Holler
2011-05-24 19:37 ` Scott Wood
2011-05-24 20:39 ` Wolfgang Denk
2011-06-14 6:18 ` Matthias Weißer
2011-06-16 16:04 ` Matthias Weisser
2011-06-30 6:31 ` Matthias Weißer
2011-07-25 22:28 ` 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=4DA69402.1020403@aribaud.net \
--to=albert.u.boot@aribaud.net \
--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.