RE: [char-misc-next] mei: request async autosuspend at the end of enumeration

> > W dniu 25.11.2016 o 04:14, Jeff King pisze: > > On Thu, Nov 24, 2016 at 10:37:14PM +, Winkler, Tomas wrote: > > > > Cc: # 4.4+ > > Looks like git send-email is not able to parse this address > correctly though this is suggested format by >

RE: [char-misc-next] mei: request async autosuspend at the end of enumeration

> > W dniu 25.11.2016 o 04:14, Jeff King pisze: > > On Thu, Nov 24, 2016 at 10:37:14PM +, Winkler, Tomas wrote: > > > > Cc: # 4.4+ > > Looks like git send-email is not able to parse this address > correctly though this is suggested format by >

Re: [char-misc-next] mei: request async autosuspend at the end of enumeration

W dniu 25.11.2016 o 04:14, Jeff King pisze: > On Thu, Nov 24, 2016 at 10:37:14PM +, Winkler, Tomas wrote: > > Cc: # 4.4+ Looks like git send-email is not able to parse this address correctly though this is suggested format by

Re: [char-misc-next] mei: request async autosuspend at the end of enumeration

W dniu 25.11.2016 o 04:14, Jeff King pisze: > On Thu, Nov 24, 2016 at 10:37:14PM +, Winkler, Tomas wrote: > > Cc: # 4.4+ Looks like git send-email is not able to parse this address correctly though this is suggested format by Documentation/stable_kernel_rules.txt.

Re: [char-misc-next] mei: request async autosuspend at the end of enumeration

On Thu, Nov 24, 2016 at 10:37:14PM +, Winkler, Tomas wrote: > > > > Cc: # 4.4+ > > > > > > Looks like git send-email is not able to parse this address correctly > > > though this is suggested format by Documentation/stable_kernel_rules.txt. > > > Create wrong address

Re: [char-misc-next] mei: request async autosuspend at the end of enumeration

On Thu, Nov 24, 2016 at 10:37:14PM +, Winkler, Tomas wrote: > > > > Cc: # 4.4+ > > > > > > Looks like git send-email is not able to parse this address correctly > > > though this is suggested format by Documentation/stable_kernel_rules.txt. > > > Create wrong address If git parsers is used :

RE: [char-misc-next] mei: request async autosuspend at the end of enumeration

> > On Thu, Nov 24, 2016 at 04:10:49PM +, Winkler, Tomas wrote: > > > > Cc: # 4.4+ > > > > Looks like git send-email is not able to parse this address correctly > > though this is suggested format by Documentation/stable_kernel_rules.txt. > > Create wrong address If

RE: [char-misc-next] mei: request async autosuspend at the end of enumeration

> > On Thu, Nov 24, 2016 at 04:10:49PM +, Winkler, Tomas wrote: > > > > Cc: # 4.4+ > > > > Looks like git send-email is not able to parse this address correctly > > though this is suggested format by Documentation/stable_kernel_rules.txt. > > Create wrong address If git parsers is used :

Re: [char-misc-next] mei: request async autosuspend at the end of enumeration

On Thu, Nov 24, 2016 at 04:10:49PM +, Winkler, Tomas wrote: > > Cc: # 4.4+ > > Looks like git send-email is not able to parse this address correctly > though this is suggested format by Documentation/stable_kernel_rules.txt. > Create wrong address If git parsers is

Re: [char-misc-next] mei: request async autosuspend at the end of enumeration

On Thu, Nov 24, 2016 at 04:10:49PM +, Winkler, Tomas wrote: > > Cc: # 4.4+ > > Looks like git send-email is not able to parse this address correctly > though this is suggested format by Documentation/stable_kernel_rules.txt. > Create wrong address If git parsers is used :

RE: [char-misc-next] mei: request async autosuspend at the end of enumeration

> > From: Alexander Usyskin > > pm_runtime_autosuspend can take synchronous or asynchronous paths, > Because we are calling pm_runtime_mark_last_busy just before this most of > the cases it takes the asynchronous way. However, when the FW or driver > resets during

RE: [char-misc-next] mei: request async autosuspend at the end of enumeration

> > From: Alexander Usyskin > > pm_runtime_autosuspend can take synchronous or asynchronous paths, > Because we are calling pm_runtime_mark_last_busy just before this most of > the cases it takes the asynchronous way. However, when the FW or driver > resets during already running runtime

[char-misc-next] mei: request async autosuspend at the end of enumeration

From: Alexander Usyskin pm_runtime_autosuspend can take synchronous or asynchronous paths, Because we are calling pm_runtime_mark_last_busy just before this most of the cases it takes the asynchronous way. However, when the FW or driver resets during already running

[char-misc-next] mei: request async autosuspend at the end of enumeration

From: Alexander Usyskin pm_runtime_autosuspend can take synchronous or asynchronous paths, Because we are calling pm_runtime_mark_last_busy just before this most of the cases it takes the asynchronous way. However, when the FW or driver resets during already running runtime suspend, the call