public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 2/7] arm1136/arm1176: Merge cache handling code
Date: Thu, 23 Jul 2015 22:52:46 -0600	[thread overview]
Message-ID: <55B1C49E.5060905@wwwdotorg.org> (raw)
In-Reply-To: <1437589418-11978-3-git-send-email-alexanders83@web.de>

On 07/22/2015 12:23 PM, Alexander Stein wrote:
> As both cores are similar merge the cache handling code for both CPUs
> to arm11 directory.

It's useful if you pass the -C or -M option to "git format-patch"; that
wouuld presumably have shown that arm11/cpu.c was identical to one of
the two cpu.c files that were deleted, making verification that the
"new" code is identical to the "old" code.

  reply	other threads:[~2015-07-24  4:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-22 18:23 [U-Boot] [PATCH v3 0/7] dcache support for Raspberry Pi 1 Alexander Stein
2015-07-22 18:23 ` [U-Boot] [PATCH v3 1/7] arm1136: Remove dead code Alexander Stein
2015-07-22 18:23 ` [U-Boot] [PATCH v3 2/7] arm1136/arm1176: Merge cache handling code Alexander Stein
2015-07-24  4:52   ` Stephen Warren [this message]
2015-07-22 18:23 ` [U-Boot] [PATCH v3 3/7] ARM: bcm283x: Define CONFIG_SYS_CACHELINE_SIZE Alexander Stein
2015-07-24  4:54   ` Stephen Warren
2015-07-22 18:23 ` [U-Boot] [PATCH v3 4/7] ARM: bcm283x: Allocate all mailbox buffers cacheline aligned Alexander Stein
2015-07-22 18:23 ` [U-Boot] [PATCH v3 5/7] arm/mach-bcm283x/mbox: Flush and invalidate dcache when using fw mailbox Alexander Stein
2015-07-22 18:23 ` [U-Boot] [PATCH v3 6/7] dwc2: Add dcache support Alexander Stein
2015-07-24  4:59   ` Stephen Warren
2015-07-22 18:23 ` [U-Boot] [PATCH v3 7/7] arm/rpi: Enable dcache Alexander Stein
2015-07-24  5:00   ` Stephen Warren

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=55B1C49E.5060905@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --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