On Thu, Mar 06, 2014 at 01:19:13PM +0900, Simon Horman wrote:
> On Fri, Feb 28, 2014 at 02:21:33PM +0100, Geert Uytterhoeven wrote:
> > From: Geert Uytterhoeven
> >
> > If cpufreq_register_notifier() fails, we have to remove the port added by
> > sci_probe_single(), which is not done by
On Fri, Feb 28, 2014 at 02:21:33PM +0100, Geert Uytterhoeven wrote:
> From: Geert Uytterhoeven
>
> If cpufreq_register_notifier() fails, we have to remove the port added by
> sci_probe_single(), which is not done by sci_cleanup_single().
>
> Else the serial port stays active from the point of
On Fri, Feb 28, 2014 at 02:21:33PM +0100, Geert Uytterhoeven wrote:
From: Geert Uytterhoeven geert+rene...@linux-m68k.org
If cpufreq_register_notifier() fails, we have to remove the port added by
sci_probe_single(), which is not done by sci_cleanup_single().
Else the serial port stays
On Thu, Mar 06, 2014 at 01:19:13PM +0900, Simon Horman wrote:
On Fri, Feb 28, 2014 at 02:21:33PM +0100, Geert Uytterhoeven wrote:
From: Geert Uytterhoeven geert+rene...@linux-m68k.org
If cpufreq_register_notifier() fails, we have to remove the port added by
sci_probe_single(), which is
From: Geert Uytterhoeven
If cpufreq_register_notifier() fails, we have to remove the port added by
sci_probe_single(), which is not done by sci_cleanup_single().
Else the serial port stays active from the point of view of the serial
subsystem, and it may crash when userspace getty is started,
From: Geert Uytterhoeven geert+rene...@linux-m68k.org
If cpufreq_register_notifier() fails, we have to remove the port added by
sci_probe_single(), which is not done by sci_cleanup_single().
Else the serial port stays active from the point of view of the serial
subsystem, and it may crash when
6 matches
Mail list logo