[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130502073020.GC26361@gmail.com>
Date: Thu, 2 May 2013 09:30:20 +0200
From: Ingo Molnar <mingo@...nel.org>
To: Robin Holt <holt@....com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
"H. Peter Anvin" <hpa@...or.com>,
Russell King <linux@....linux.org.uk>,
Guan Xuetao <gxt@...c.pku.edu.cn>,
Miguel Boton <mboton.lkml@...il.com>,
Russ Anderson <rja@....com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
the arch/x86 maintainers <x86@...nel.org>,
Arm Mailing List <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH -v7 10/11] arm, change reboot_mode to use enum reboot_mode
* Robin Holt <holt@....com> wrote:
> #ifndef __ASSEMBLY__
>
> #include <linux/types.h>
> +#include <linux/reboot.h>
>
> void iop3xx_map_io(void);
> void iop_init_cp6_handler(void);
> void iop_init_time(unsigned long tickrate);
> -void iop3xx_restart(char, const char *);
> +void iop3xx_restart(enum reboot_mode, const char *);
IMO the introduction of the enum is making things cleaner here all around.
As long as it's an equivalent transformation for ARM with no reduction in
functionality (i.e. please fix any bugs Russell found), this all looks
like a nice series.
Is there no parameter namespace clash between reboot modifier strings on
various architectures? I.e. 's' meaning something on x86 and meaning a
different thing on ARM or some other architecture.
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists