From: Andrey Panin <pazke@donpac.ru>
To: Hirokazu Takata <takata@linux-m32r.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] m32r - Upgrade to v2.6.6 kernel
Date: Fri, 28 May 2004 11:23:36 +0400 [thread overview]
Message-ID: <20040528072336.GD7499@pazke> (raw)
In-Reply-To: <20040528.131611.28785624.takata.hirokazu@renesas.com>
[-- Attachment #1: Type: text/plain, Size: 2607 bytes --]
On 149, 05 28, 2004 at 01:16:11PM +0900, Hirokazu Takata wrote:
> Hello,
>
> I would like to send the latest 2.6.6 kernel patch for
> the Renesas M32R processor.
>
> Patch information to the stock 2.6.6 kernel is placed as follows:
> - m32r architecture dependent portions (arch/m32r, include/asm-m32r)
> http://www.linux-m32r.org/public/linux-2.6.6_m32r_20040528.arch-m32r.patch
Single megapatch (1.5 Mb in size) is not the best way to merge something into Linux kernel.
Now quick look at the patch itself:
1)
diff -ruN linux-2.6.6.org/arch/m32r/drivers/8390.c linux-2.6.6/arch/m32r/drivers/8390.c
--- linux-2.6.6.org/arch/m32r/drivers/8390.c 1970-01-01 09:00:00.000000000 +0900
+++ linux-2.6.6/arch/m32r/drivers/8390.c 2003-09-09 10:15:02.000000000 +0900
@@ -0,0 +1 @@
+#include "../../../drivers/net/8390.c"
diff -ruN linux-2.6.6.org/arch/m32r/drivers/8390.h linux-2.6.6/arch/m32r/drivers/8390.h
--- linux-2.6.6.org/arch/m32r/drivers/8390.h 1970-01-01 09:00:00.000000000 +0900
+++ linux-2.6.6/arch/m32r/drivers/8390.h 2003-09-09 10:15:02.000000000 +0900
@@ -0,0 +1 @@
+#include "../../../drivers/net/8390.h"
Is this really needed ?
2) File arch/m32r/drivers/mappi_ne.c contains almost complete copy of drivers/net/ne.c
with lots of code probably useless for your systems (old style ISA probing, ISAPnP
support etc.)
Also code like this is definetely unacceptable:
+#ifdef CONFIG_PLAT_MAPPI
+ outb_p(0x4b, ioaddr + EN0_DCFG);
+#elif CONFIG_PLAT_OAKS32R
+ outb_p(0x48, ioaddr + EN0_DCFG);
+#else
+ outb_p(0x49, ioaddr + EN0_DCFG);
+#endif
This fragment can be rewritten this way, with all #ifdef mess hidden in the some header file:
+ outb_p(MY_MAGIC_OFFSET, ioaddr + EN0_DCFG);
3) arch/m32r/drivers/smc91111.copying contains GPL copy. Do you really need it ?
arch/m32r/drivers/smc91111.readme.txt can happily live in Documentation/networking.
4) Do you really need to reimplement Linux console subsystem in arch/m32r/drivers/video/console.c,
arch/m32r/drivers/video/fbmem.c, arch/m32r/drivers/video/fbcon.h ?
5) Any specific reason to implement read[bwl]/write[bwl] this way:
+unsigned char _readb(unsigned long addr)
+{
+ return *(volatile unsigned char *)addr;
+}
Why not to inline them ?
6) Lots of ugly debugging #ifdef's in arch/m32r/kernel/ptrace.c
7) arch/m32r/lib/clib.c contains slightly strange abs() function which
isn't used anywhere in the patch.
Best reards.
--
Andrey Panin | Linux and UNIX system administrator
pazke@donpac.ru | PGP key: wwwkeys.pgp.net
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-05-28 7:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-28 4:16 [PATCH] m32r - Upgrade to v2.6.6 kernel Hirokazu Takata
2004-05-28 7:23 ` Andrey Panin [this message]
2004-05-28 7:48 ` Russell King
2004-05-28 13:53 ` Hirokazu Takata
2004-06-02 2:40 ` Miles Bader
2004-05-28 12:21 ` Hirokazu Takata
2004-05-28 14:15 ` Andrey Panin
2004-05-29 2:15 ` Hirokazu Takata
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=20040528072336.GD7499@pazke \
--to=pazke@donpac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=takata@linux-m32r.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.