From: "David Müller (ELSOFT AG)" <d.mueller@elsoft.ch>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: [PATCH] Various patches against linuxppc_dev-2.4.13-pre6
Date: Wed, 24 Oct 2001 13:52:09 +0200 [thread overview]
Message-ID: <3BD6AB69.5010704@elsoft.ch> (raw)
In-Reply-To: 20011023073258.B30012@cpe-24-221-152-185.az.sprintbbd.net
Tom Rini wrote:
> On Tue, Oct 23, 2001 at 08:25:18AM +0200, David M?ller (ELSOFT AG) wrote:
>
>
>>Hello again
>>
>>The attached patch fixes the following issues:
>>
>> - arch/ppc/mm/fault.c
>> missing get_pteptr() prototype
>>
>
> Applied.
>
>
>> - arch/ppc/kernel/i8259.c
>> consistent nameing (rather cosmetic change)
>>
>
> Not sure about. Why either of those changes?
>
The first patch is just a prettyprint fix. At least on my system
it looks better this way ;-)
Everywhere in the i8259.[ch] files the chip is called "i8259" with the
exception of one place which is fixed by the second patch. But as
i said, it's more of a cosmetic change.
>
>> - arch/ppc/ppc_ksyms.c
>> missing flush_dcache_all() export
>>
>
> This only exists on CONFIG_NOT_CACHE_COHERENT, fixed and applied.
>
>
>> - 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
>>
>
> Applied.
>
> Thanks!
>
>
Dave
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-10-24 11:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-23 6:25 [PATCH] Various patches against linuxppc_dev-2.4.13-pre6 David Müller (ELSOFT AG)
2001-10-23 14:32 ` Tom Rini
2001-10-24 11:52 ` David Müller (ELSOFT AG) [this message]
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=3BD6AB69.5010704@elsoft.ch \
--to=d.mueller@elsoft.ch \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=trini@kernel.crashing.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).