From: "David Müller (ELSOFT AG)" <d.mueller@elsoft.ch>
To: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: [PATCH] Several patches against linuxppc_devel-2.4.18-pre9
Date: Mon, 11 Feb 2002 15:32:14 +0100 [thread overview]
Message-ID: <3C67D5EE.70008@elsoft.ch> (raw)
[-- Attachment #1: Type: text/plain, Size: 562 bytes --]
Hello
The attached patch fixes the following issues:
- drivers/net/ibm_ocp_enet.c
wrong prototypes + initialisation in debug code
- drivers/net/ibm_ocp_enet.h
missing prototypes for [get|set]_maltxdeir()
missing prototypes for [get|set]_maltxctp1r()
- drivers/net/ibm_ocp_phy.c
workaround for MII-PHY communication bug reported by Andrew May
- arch/ppc/mm/fault.c
missing type cast
- arch/ppc/mm/cachemap.c
missing prototype for map_page() (added mmu_decl.h)
2 missing type casts
Dave
[-- Attachment #2: linuxppc.patch.bz2 --]
[-- Type: application/octet-stream, Size: 1435 bytes --]
next reply other threads:[~2002-02-11 14:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-11 14:32 David Müller (ELSOFT AG) [this message]
2002-02-11 9:29 ` [PATCH] Several patches against linuxppc_devel-2.4.18-pre9 Armin
2002-02-11 18:10 ` Stefan Roese
2002-02-11 11:34 ` Armin
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=3C67D5EE.70008@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).