On Thu, Jul 09 2015 at 02:33 -0600, Jisheng Zhang wrote:
As for the suspend member function, the to-be-suspended cpu is always
the calling cpu itself, so the 'cpu' parameter may not be necessary, let
driver get 'cpu' itself if need.
As for the init member function, the device_node here may not
On Thu, Jul 09 2015 at 03:28 -0600, Lorenzo Pieralisi wrote:
On Thu, Jul 09, 2015 at 09:43:04AM +0100, Jisheng Zhang wrote:
On Thu, 9 Jul 2015 16:31:24 +0800
Jisheng Zhang wrote:
> As for the suspend member function, the to-be-suspended cpu is always
> the calling cpu itself, so the 'cpu'
On Thu, Jul 09 2015 at 03:28 -0600, Lorenzo Pieralisi wrote:
On Thu, Jul 09, 2015 at 09:43:04AM +0100, Jisheng Zhang wrote:
On Thu, 9 Jul 2015 16:31:24 +0800
Jisheng Zhang jszh...@marvell.com wrote:
As for the suspend member function, the to-be-suspended cpu is always
the calling cpu itself,
On Thu, Jul 09 2015 at 02:33 -0600, Jisheng Zhang wrote:
As for the suspend member function, the to-be-suspended cpu is always
the calling cpu itself, so the 'cpu' parameter may not be necessary, let
driver get 'cpu' itself if need.
As for the init member function, the device_node here may not
On Thu, Jul 09, 2015 at 09:43:04AM +0100, Jisheng Zhang wrote:
> On Thu, 9 Jul 2015 16:31:24 +0800
> Jisheng Zhang wrote:
>
> > As for the suspend member function, the to-be-suspended cpu is always
> > the calling cpu itself, so the 'cpu' parameter may not be necessary, let
> > driver get 'cpu'
On Thu, 9 Jul 2015 16:31:24 +0800
Jisheng Zhang wrote:
> As for the suspend member function, the to-be-suspended cpu is always
> the calling cpu itself, so the 'cpu' parameter may not be necessary, let
> driver get 'cpu' itself if need.
>
> As for the init member function, the device_node here
As for the suspend member function, the to-be-suspended cpu is always
the calling cpu itself, so the 'cpu' parameter may not be necessary, let
driver get 'cpu' itself if need.
As for the init member function, the device_node here may not be
necessary either, because we can get the node via.
On Thu, 9 Jul 2015 16:31:24 +0800
Jisheng Zhang jszh...@marvell.com wrote:
As for the suspend member function, the to-be-suspended cpu is always
the calling cpu itself, so the 'cpu' parameter may not be necessary, let
driver get 'cpu' itself if need.
As for the init member function, the
As for the suspend member function, the to-be-suspended cpu is always
the calling cpu itself, so the 'cpu' parameter may not be necessary, let
driver get 'cpu' itself if need.
As for the init member function, the device_node here may not be
necessary either, because we can get the node via.
On Thu, Jul 09, 2015 at 09:43:04AM +0100, Jisheng Zhang wrote:
On Thu, 9 Jul 2015 16:31:24 +0800
Jisheng Zhang jszh...@marvell.com wrote:
As for the suspend member function, the to-be-suspended cpu is always
the calling cpu itself, so the 'cpu' parameter may not be necessary, let
driver
10 matches
Mail list logo