From: Ralf Baechle <ralf@linux-mips.org>
To: Shinya Kuribayashi <skuribay@ruby.dti.ne.jp>
Cc: linux-mips@linux-mips.org, shinya.kuribayashi@necel.com
Subject: Re: [PATCH 00/10] Restructure EMMA2RH port
Date: Mon, 27 Oct 2008 10:47:50 +0000 [thread overview]
Message-ID: <20081027104749.GA9554@linux-mips.org> (raw)
In-Reply-To: <4900A510.3000101@ruby.dti.ne.jp>
On Fri, Oct 24, 2008 at 01:23:44AM +0900, Shinya Kuribayashi wrote:
Shinya-San,
> there have been many NEC EMMA SoCs so far, and with great pleasure we
> have many Linux ports running on EMMA these days. Even though most
> those ports are not submitted to upstream, but I'd like to reorganize
> current EMMA2RH ports into more easy maintainable shape as a reference.
And I hope more of the code for the reference platforms to be submitted
in the future!
> There are a lot of things to do. For the first step, I'd like to
> introduce arch/mips/emma/ and include/asm/emma/ directories so that all
> EMMA related sourches/headers can be easily shared across various EMMA
> products/ports.
>
> Here's the first attempt to try to change things as mentioned above.
> Some possible improvements and cleanups are also included. Patches will
> follow, please review. Any comments are highly appreciated.
Full series applied.
> P.S. I'm also planning to do more cleanups around IRQ codes, register
> definition style, and so on. But that'll be some other time.
Whenever you're ready!
Thanks,
Ralf
next prev parent reply other threads:[~2008-10-27 10:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-23 16:23 [PATCH 00/10] Restructure EMMA2RH port Shinya Kuribayashi
2008-10-23 16:27 ` [PATCH 01/12] MIPS: Add CONFIG_CPU_R5500 for NEC VR5500 series processors Shinya Kuribayashi
2008-10-23 16:29 ` [PATCH 03/12] MIPS: Move arch/mips/emma2rh/ into arch/mips/emma/ Shinya Kuribayashi
2008-10-23 16:30 ` [PATCH 04/12] MIPS: Move <asm/emma2rh> to <asm/emma> dir Shinya Kuribayashi
2008-10-27 15:07 ` [PATCH] MIPS: EMMA2RH: Fix incorrect header references Shinya Kuribayashi
2008-10-27 15:36 ` Ralf Baechle
2008-10-23 16:30 ` [PATCH 05/12] MIPS: Remove emma2rh_sync on read operation Shinya Kuribayashi
2008-10-23 16:31 ` [PATCH 06/12] MIPS: EMMA2RH: Remove emma2rh_irq_base global variable Shinya Kuribayashi
2008-10-23 16:31 ` [PATCH 07/12] MIPS: EMMA2RH: Remove emma2rh_sw_irq_base Shinya Kuribayashi
2008-10-23 16:32 ` [PATCH 08/12] MIPS: EMMA2RH: Remove emma2rh_gpio_irq_base Shinya Kuribayashi
2008-10-23 17:20 ` Markus Gothe
2008-10-23 16:32 ` [PATCH 09/12] MIPS: Fold arch/mips/emma/{common,markeins}/irq*.c into markeins/irq.c Shinya Kuribayashi
2008-10-23 16:33 ` [PATCH 10/12] MIPS: Markeins: Remove runtime debug prints Shinya Kuribayashi
2008-10-23 16:35 ` [PATCH 11/12] MIPS: Markeins: Extract ll_emma2rh_* functions Shinya Kuribayashi
2008-10-23 16:36 ` [PATCH 12/12] MIPS: Markeins: Remove unnecessary define and cleanup comments, etc Shinya Kuribayashi
2008-10-23 21:00 ` [PATCH 02/12] MIPS: EMMA Kconfig reorganization Shinya Kuribayashi
2008-10-27 10:47 ` Ralf Baechle [this message]
2008-10-27 11:05 ` [PATCH 00/10] Restructure EMMA2RH port Shinya Kuribayashi
2008-10-27 14:50 ` Ralf Baechle
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=20081027104749.GA9554@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=shinya.kuribayashi@necel.com \
--cc=skuribay@ruby.dti.ne.jp \
/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