From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] PPC440EPx/sequoia TLB question...
Date: Tue, 29 Apr 2008 07:54:33 +0200 [thread overview]
Message-ID: <200804290754.33134.sr@denx.de> (raw)
In-Reply-To: <48128B6B.8090909@verizon.net>
On Saturday 26 April 2008, Dave Littell wrote:
> Here goes (again):
>
> Patch for AMCC Sequoia to remove the TLB Guarded attribute for SDRAM,
> and add the Guarded attribute for Internal Registers & OCM.
I still have a few issues with this patch:
- Signed-off-by line missing
- Please use a descriptive subject for this patch, something like:
"[PATCH] ppc4xx: Fix guarded bit in some Sequoia TLB entries"
- Comments that should not be part of the commit text should go
below the "---" line in the email. Please take a look at other
patches sent to the list on how exactly this should be done.
- And best would be to create two separate TLB entries, one for
internal SRAM (OCM) with G cleared and one for internal registers
with G set
I strongly suggest to work with the git tools to create and send patches. This
makes life a lot easier for all of us.
Thanks.
Best regards,
Stefan
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
prev parent reply other threads:[~2008-04-29 5:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 3:11 [U-Boot-Users] PPC440EPx/sequoia TLB question Dave Littell
2008-04-23 12:42 ` Stefan Roese
2008-04-24 2:27 ` Dave Littell
2008-04-24 5:28 ` Stefan Roese
2008-04-24 11:58 ` Josh Boyer
2008-04-24 13:07 ` Stefan Roese
2008-04-25 2:34 ` [U-Boot-Users] [PATCH] " Dave Littell
2008-04-25 5:31 ` Stefan Roese
2008-04-26 1:54 ` [U-Boot-Users] " Dave Littell
2008-04-29 5:54 ` Stefan Roese [this message]
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=200804290754.33134.sr@denx.de \
--to=sr@denx.de \
--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