From: Joe Perches <joe@perches.com>
To: Yoshinori Sato <ysato@users.sourceforge.jp>
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: [PATCH v6 06/16] h8300: CPU depend helpers
Date: Mon, 09 Mar 2015 09:21:07 -0700 [thread overview]
Message-ID: <1425918067.5428.10.camel@perches.com> (raw)
In-Reply-To: <1425890830-29399-7-git-send-email-ysato@users.sourceforge.jp>
On Mon, 2015-03-09 at 17:47 +0900, Yoshinori Sato wrote:
> Signed-off-by: Yoshinori Sato <ysato@users.sourceforge.jp>
trivia:
> arch/h8300/kernel/cpu/h83069/setup.c | 202 ++++++++++++++++++++++++++
[]
> diff --git a/arch/h8300/kernel/cpu/h83069/setup.c b/arch/h8300/kernel/cpu/h83069/setup.c
[]
> +static struct resource sci0_resources[] = {
> + DEFINE_RES_MEM(0xffffb0, 8),
> + DEFINE_RES_IRQ(52),
> + DEFINE_RES_IRQ(53),
> + DEFINE_RES_IRQ(54),
> + DEFINE_RES_IRQ(55),
> +}
Perhaps most all of these might be const?
> +static struct plat_sci_port sci0_platform_data = {
[]
> +static struct resource sci1_resources[] = {
[]
> +static struct plat_sci_port sci1_platform_data = {
[]
> +static struct platform_device sci0_device = {
[]
> +static struct platform_device sci1_device = {
[]
> +static struct h8300_timer8_config tm8_unit0_platform_data = {
[]
> +static struct resource tm8_unit0_resources[] = {
[]
> +static struct platform_device timer8_unit0_device = {
[]
> +static struct h8300_timer8_config tm8_unit1_platform_data = {
[]
etc..
next prev parent reply other threads:[~2015-03-09 16:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 8:46 [PATCH v6 00/16] Revert h8300 archtecture support Yoshinori Sato
2015-03-09 8:46 ` [PATCH v6 01/16] h8300: Assembly headers Yoshinori Sato
2015-03-09 8:46 ` [PATCH v6 02/16] h8300: UAPI headers Yoshinori Sato
2015-03-09 8:46 ` [PATCH v6 03/16] h8300: Exception and Interrupt handling Yoshinori Sato
2015-03-09 8:46 ` [PATCH v6 04/16] h8300: kernel booting Yoshinori Sato
2015-03-09 8:46 ` [PATCH v6 05/16] h8300: Process and signal Yoshinori Sato
2015-03-09 8:47 ` [PATCH v6 06/16] h8300: CPU depend helpers Yoshinori Sato
2015-03-09 16:21 ` Joe Perches [this message]
2015-03-09 17:55 ` Geert Uytterhoeven
2015-03-09 8:47 ` [PATCH v6 07/16] h8300: miscellaneous functions Yoshinori Sato
2015-03-09 8:47 ` [PATCH v6 08/16] h8300: Memory management Yoshinori Sato
2015-03-09 8:47 ` [PATCH v6 09/16] h8300: library functions Yoshinori Sato
2015-03-09 8:47 ` [PATCH v6 10/16] h8300: Build scripts Yoshinori Sato
2015-03-09 8:47 ` [PATCH v6 11/16] h8300: clock driver Yoshinori Sato
2015-03-09 9:13 ` Jeff Kirsher
2015-03-10 7:46 ` Yoshinori Sato
2015-03-09 8:47 ` [PATCH v6 12/16] h8300: clocksource Yoshinori Sato
2015-03-09 8:47 ` [PATCH v6 13/16] h8300: configs Yoshinori Sato
2015-03-09 8:47 ` [PATCH v6 14/16] serial: Add h8300 Yoshinori Sato
2015-03-09 8:47 ` [PATCH v6 15/16] Add ELF machine Yoshinori Sato
2015-03-09 9:10 ` Jeff Kirsher
2015-03-10 7:43 ` Yoshinori Sato
2015-03-09 8:47 ` [PATCH v6 16/16] mksysmap: Add h8300 local symbol pattern Yoshinori Sato
2015-03-10 5:55 ` [PATCH v6 00/16] Revert h8300 archtecture support Guenter Roeck
2015-03-10 8:09 ` Yoshinori Sato
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=1425918067.5428.10.camel@perches.com \
--to=joe@perches.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ysato@users.sourceforge.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;
as well as URLs for NNTP newsgroup(s).