All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCHv2 1/2] mpc85xx: Initial SP alignment is wrong.
Date: Thu, 23 Aug 2012 11:53:14 -0500	[thread overview]
Message-ID: <50365FFA.8070904@freescale.com> (raw)
In-Reply-To: <OFEE7C5D09.895361EC-ONC1257A63.002807AC-C1257A63.002866B7@transmode.se>

On 08/23/2012 02:21 AM, Joakim Tjernlund wrote:
> Andy Fleming <afleming@gmail.com> wrote on 2012/08/22 23:08:45:
>>
>> On Mon, Jul 23, 2012 at 3:58 PM, Joakim Tjernlund
>> <Joakim.Tjernlund@transmode.se> wrote:
>>> PowerPC mandates SP to be 16 bytes aligned.
>>> Furthermore, a stack frame is added, pointing to the reset vector
>>> which may in the way when gdb is walking the stack because
>>> the reset vector may not accessible depending on emulator settings.
>>> Also use a temp register so gdb doesn't pick up intermediate values.
>>>
>>> Signed-off-by: Joakim Tjernlund <Joakim.Tjernlund@transmode.se>
>>> ---
>>>
>>>  v2 - Address Scott Wood's comments
>>>  arch/powerpc/cpu/mpc85xx/start.S |   16 +++++-----------
>>>  1 files changed, 5 insertions(+), 11 deletions(-)
>>>
>>> diff --git arch/powerpc/cpu/mpc85xx/start.S arch/powerpc/cpu/mpc85xx/start.S
>>
>>
>> Why are your patches different from everyone else's? When I try to
>> apply this, I get errors because it can't find
>> "powerpc/cpu/mpc85xx...". git am leaves off the first directory,
>> because the usual practice is to send patches with these filenames:
> 
> Ahh, recently I set (in ny git config):
> [diff]
> 	noprefix = true
> because I got tired off stripping off that prefix each time I cut and
> paste file names into emacs and similar.
> 
> Seems like git really likes to see that prefix when applying patches.
> Don't know if git could learn not to complain about missing prefix?

It's not just git, but also direct use of the patch command when a patch
fails to apply cleanly.  A user shouldn't have to inspect a patch to
determine whether to use -p0 or -p1.  -p1 is standard.

How often do you copy and paste filenames out of your own patches?

-Scott

  reply	other threads:[~2012-08-23 16:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-23 20:58 [U-Boot] [PATCHv2 1/2] mpc85xx: Initial SP alignment is wrong Joakim Tjernlund
2012-07-23 20:58 ` [U-Boot] [PATCHv2 2/2] powerpc: Stack Pointer not properly aligned Joakim Tjernlund
2012-08-14 20:55   ` Joakim Tjernlund
2012-08-14 20:55 ` [U-Boot] [PATCHv2 1/2] mpc85xx: Initial SP alignment is wrong Joakim Tjernlund
2012-08-14 21:01   ` Scott Wood
2012-08-15  7:05     ` Joakim Tjernlund
2012-08-14 21:28 ` Kumar Gala
2012-08-15  7:10   ` Joakim Tjernlund
2012-08-15 17:13     ` Scott Wood
2012-08-16 23:40       ` Andy Fleming
2012-08-22 21:08 ` Andy Fleming
2012-08-23  7:21   ` Joakim Tjernlund
2012-08-23 16:53     ` Scott Wood [this message]
2012-08-23 18:51       ` Joakim Tjernlund

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=50365FFA.8070904@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 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.