From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>
Subject: [Fwd: PATCH: comment change against linuxppc-2.5 BK tree arch/ppc/platforms/4xx/ibm405lp.h (fwd)]
Date: Fri, 21 Nov 2003 10:55:59 +1100 [thread overview]
Message-ID: <1069372559.703.38.camel@gaston> (raw)
-----Forwarded Message-----
From: "Verberk, Bep" <verberk@nortelnetworks.com>
Subject: PATCH: comment change against linuxppc-2.5 BK tree arch/ppc/platforms/4xx/ibm405lp.h (fwd)
Date: Tue, 18 Nov 2003 16:39:20 -0500
Gents,
this is a trivial change.
I wouldn't have bothered but its my first ever kernel change and
I wanted to pipe-clean my understanding of the process.
Not sure if diff-ing it
against the latest BK snapshot is OK. Let me know I can re-do it.
I've just started going through the 405 code so I may have
more input later and I'd like to make sure I'm submitting it properly.
Now I'll go try to find a real bug :)
Cheers,
Bep
diff -urN linuxppc-2.5/arch/ppc/platforms/4xx/ibm405lp.h
linux/arch/ppc/platforms/4xx/ibm405lp.h
--- linuxppc-2.5/arch/ppc/platforms/4xx/ibm405lp.h 2003-11-18
16:08:11.000000000 -0500
+++ linux/arch/ppc/platforms/4xx/ibm405lp.h 2003-11-18
16:19:10.000000000 -0500
@@ -199,7 +199,7 @@
#define DCRN_EBC0_B7AP 0x17 /* Peripheral Bank 7 Access Parameters */
#define DCRN_EBC0_BEAR 0x20 /* Periperal Bus Error Address Register */
#define DCRN_EBC0_BESR0 0x21 /* Peripheral Bus Error Status Register 0 */
-#define DCRN_EBC0_BESR1 0x22 /* Peripheral Bus Error Status Register 0 */
+#define DCRN_EBC0_BESR1 0x22 /* Peripheral Bus Error Status Register 1 */
#define DCRN_EBC0_CFG 0x23 /* External Peripheral Control Register */
#define EBC0_BANKS 8
--
Benjamin Herrenschmidt <benh@kernel.crashing.org>
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
reply other threads:[~2003-11-20 23:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1069372559.703.38.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
/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;
as well as URLs for NNTP newsgroup(s).