Re: [PATCH] hvc: ensure hvc_init is only ever called once in hvc_console.c

2014-01-14 Thread Greg Kroah-Hartman
On Tue, Jan 14, 2014 at 04:03:37PM -0500, Paul Gortmaker wrote: > Commit 3e6c6f630a5282df8f3393a59f10eb9c56536d23 ("Delay creation of > khcvd thread") moved the call of hvc_init from being a device_initcall > into hvc_alloc, and used a non-null hvc_driver as indication of whether > hvc_init had

[PATCH] hvc: ensure hvc_init is only ever called once in hvc_console.c

2014-01-14 Thread Paul Gortmaker
Commit 3e6c6f630a5282df8f3393a59f10eb9c56536d23 ("Delay creation of khcvd thread") moved the call of hvc_init from being a device_initcall into hvc_alloc, and used a non-null hvc_driver as indication of whether hvc_init had already been called. The problem with this is that hvc_driver is only

[PATCH] hvc: ensure hvc_init is only ever called once in hvc_console.c

2014-01-14 Thread Paul Gortmaker
Commit 3e6c6f630a5282df8f3393a59f10eb9c56536d23 (Delay creation of khcvd thread) moved the call of hvc_init from being a device_initcall into hvc_alloc, and used a non-null hvc_driver as indication of whether hvc_init had already been called. The problem with this is that hvc_driver is only

Re: [PATCH] hvc: ensure hvc_init is only ever called once in hvc_console.c

2014-01-14 Thread Greg Kroah-Hartman
On Tue, Jan 14, 2014 at 04:03:37PM -0500, Paul Gortmaker wrote: Commit 3e6c6f630a5282df8f3393a59f10eb9c56536d23 (Delay creation of khcvd thread) moved the call of hvc_init from being a device_initcall into hvc_alloc, and used a non-null hvc_driver as indication of whether hvc_init had already