On Wed, Apr 02, 2014 at 04:18:57PM -0700, Greg Kroah-Hartman wrote:
> On Wed, Apr 02, 2014 at 09:38:06AM +0300, Peter Ujfalusi wrote:
> > Do you want me to resend this patch in hope that it is going to be taken or
> > do
> > you have other method in mind to deal with the situation I have
On Wed, Apr 02, 2014 at 04:18:57PM -0700, Greg Kroah-Hartman wrote:
On Wed, Apr 02, 2014 at 09:38:06AM +0300, Peter Ujfalusi wrote:
Do you want me to resend this patch in hope that it is going to be taken or
do
you have other method in mind to deal with the situation I have described
On Wed, Apr 02, 2014 at 09:38:06AM +0300, Peter Ujfalusi wrote:
> Hi Greg,
>
> On 03/04/2014 06:56 AM, Mark Brown wrote:
> > On Mon, Mar 03, 2014 at 10:26:59AM +0200, Peter Ujfalusi wrote:
> >
> >> I think it is correct to detect this situation without the need to have non
> >> related drivers
Hi Greg,
On 03/04/2014 06:56 AM, Mark Brown wrote:
> On Mon, Mar 03, 2014 at 10:26:59AM +0200, Peter Ujfalusi wrote:
>
>> I think it is correct to detect this situation without the need to have non
>> related drivers to be probed.
>> The patch is doing this exactly: detects if we had successful
Hi Greg,
On 03/04/2014 06:56 AM, Mark Brown wrote:
On Mon, Mar 03, 2014 at 10:26:59AM +0200, Peter Ujfalusi wrote:
I think it is correct to detect this situation without the need to have non
related drivers to be probed.
The patch is doing this exactly: detects if we had successful parallel
On Wed, Apr 02, 2014 at 09:38:06AM +0300, Peter Ujfalusi wrote:
Hi Greg,
On 03/04/2014 06:56 AM, Mark Brown wrote:
On Mon, Mar 03, 2014 at 10:26:59AM +0200, Peter Ujfalusi wrote:
I think it is correct to detect this situation without the need to have non
related drivers to be probed.
On Mon, Mar 03, 2014 at 10:26:59AM +0200, Peter Ujfalusi wrote:
> I think it is correct to detect this situation without the need to have non
> related drivers to be probed.
> The patch is doing this exactly: detects if we had successful parallel driver
> probe(s) while another driver was probing
On 03/01/2014 02:33 AM, Greg Kroah-Hartman wrote:
> On Wed, Feb 26, 2014 at 09:06:54AM +0200, Peter Ujfalusi wrote:
>> When the kernel is built with CONFIG_PREEMPT it is possible to reach a state
>> when all modules are loaded but some driver still stuck in the deferred list
>> and there is a need
On 03/01/2014 02:33 AM, Greg Kroah-Hartman wrote:
On Wed, Feb 26, 2014 at 09:06:54AM +0200, Peter Ujfalusi wrote:
When the kernel is built with CONFIG_PREEMPT it is possible to reach a state
when all modules are loaded but some driver still stuck in the deferred list
and there is a need for
On Mon, Mar 03, 2014 at 10:26:59AM +0200, Peter Ujfalusi wrote:
I think it is correct to detect this situation without the need to have non
related drivers to be probed.
The patch is doing this exactly: detects if we had successful parallel driver
probe(s) while another driver was probing
On Wed, Feb 26, 2014 at 09:06:54AM +0200, Peter Ujfalusi wrote:
> When the kernel is built with CONFIG_PREEMPT it is possible to reach a state
> when all modules are loaded but some driver still stuck in the deferred list
> and there is a need for external event to kick the deferred queue to probe
On Wed, Feb 26, 2014 at 09:06:54AM +0200, Peter Ujfalusi wrote:
When the kernel is built with CONFIG_PREEMPT it is possible to reach a state
when all modules are loaded but some driver still stuck in the deferred list
and there is a need for external event to kick the deferred queue to probe
When the kernel is built with CONFIG_PREEMPT it is possible to reach a state
when all modules are loaded but some driver still stuck in the deferred list
and there is a need for external event to kick the deferred queue to probe
these drivers.
The issue has been observed on embedded systems with
When the kernel is built with CONFIG_PREEMPT it is possible to reach a state
when all modules are loaded but some driver still stuck in the deferred list
and there is a need for external event to kick the deferred queue to probe
these drivers.
The issue has been observed on embedded systems with
14 matches
Mail list logo
