From: "David Müller (ELSOFT AG)" <d.mueller@elsoft.ch>
To: linuxppc-embedded@lists.linuxppc.org
Subject: [PATCH] Various patches against linuxppc_dev-2.4.13-pre6
Date: Tue, 23 Oct 2001 08:25:18 +0200 [thread overview]
Message-ID: <3BD50D4E.6060401@elsoft.ch> (raw)
[-- Attachment #1: Type: text/plain, Size: 463 bytes --]
Hello again
The attached patch fixes the following issues:
- arch/ppc/mm/fault.c
missing get_pteptr() prototype
- arch/ppc/kernel/i8259.c
consistent nameing (rather cosmetic change)
- arch/ppc/ppc_ksyms.c
missing flush_dcache_all() export
- arch/ppc/kernel/ppc4xx_setup.c
added "l" format flag to sprintf() to make compiler happy
(cosmetic)
- arch/ppc/kernel/ppc405_pci.c
adjust include file name
Dave
[-- Attachment #2: various_patches-1.bz2 --]
[-- Type: application/octet-stream, Size: 1203 bytes --]
next reply other threads:[~2001-10-23 6:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-23 6:25 David Müller (ELSOFT AG) [this message]
2001-10-23 14:32 ` [PATCH] Various patches against linuxppc_dev-2.4.13-pre6 Tom Rini
2001-10-24 11:52 ` David Müller (ELSOFT AG)
2001-10-24 22:48 ` Tom Rini
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=3BD50D4E.6060401@elsoft.ch \
--to=d.mueller@elsoft.ch \
--cc=linuxppc-embedded@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).