Hi Mark,
On 8 December 2016 at 19:04, Mark Rutland wrote:
> On Thu, Dec 08, 2016 at 11:16:21AM +0800, Fu Wei wrote:
>> Hi Timur,
>>
>> On 8 December 2016 at 01:25, Timur Tabi wrote:
>> > On Fri, Nov 25, 2016 at 9:06 AM, Fu Wei
Hi Mark,
On 8 December 2016 at 19:04, Mark Rutland wrote:
> On Thu, Dec 08, 2016 at 11:16:21AM +0800, Fu Wei wrote:
>> Hi Timur,
>>
>> On 8 December 2016 at 01:25, Timur Tabi wrote:
>> > On Fri, Nov 25, 2016 at 9:06 AM, Fu Wei wrote:
>> >>
>> >> a "+ int ret;" should be move from [12/15] to
On Thu, Dec 08, 2016 at 11:16:21AM +0800, Fu Wei wrote:
> Hi Timur,
>
> On 8 December 2016 at 01:25, Timur Tabi wrote:
> > On Fri, Nov 25, 2016 at 9:06 AM, Fu Wei wrote:
> >>
> >> a "+ int ret;" should be move from [12/15] to here, I have fix the
> >>
On Thu, Dec 08, 2016 at 11:16:21AM +0800, Fu Wei wrote:
> Hi Timur,
>
> On 8 December 2016 at 01:25, Timur Tabi wrote:
> > On Fri, Nov 25, 2016 at 9:06 AM, Fu Wei wrote:
> >>
> >> a "+ int ret;" should be move from [12/15] to here, I have fix the
> >> problem in my repo, it would happen in next
Hi Timur,
On 8 December 2016 at 01:25, Timur Tabi wrote:
> On Fri, Nov 25, 2016 at 9:06 AM, Fu Wei wrote:
>>
>> a "+ int ret;" should be move from [12/15] to here, I have fix the
>> problem in my repo, it would happen in next patchset
>>
>>
Hi Timur,
On 8 December 2016 at 01:25, Timur Tabi wrote:
> On Fri, Nov 25, 2016 at 9:06 AM, Fu Wei wrote:
>>
>> a "+ int ret;" should be move from [12/15] to here, I have fix the
>> problem in my repo, it would happen in next patchset
>>
>>
On Fri, Nov 25, 2016 at 9:06 AM, Fu Wei wrote:
>
> a "+ int ret;" should be move from [12/15] to here, I have fix the
> problem in my repo, it would happen in next patchset
>
> https://git.linaro.org/people/fu.wei/linux.git/log/?h=topic-gtdt-wakeup-timer_upstream_v18_devel
Fu,
On Fri, Nov 25, 2016 at 9:06 AM, Fu Wei wrote:
>
> a "+ int ret;" should be move from [12/15] to here, I have fix the
> problem in my repo, it would happen in next patchset
>
> https://git.linaro.org/people/fu.wei/linux.git/log/?h=topic-gtdt-wakeup-timer_upstream_v18_devel
Fu, please post v18 to
Hi ,
On 25 November 2016 at 22:32, kbuild test robot wrote:
> Hi Fu,
>
> [auto build test ERROR on pm/linux-next]
> [also build test ERROR on v4.9-rc6]
> [cannot apply to tip/timers/core next-20161125]
> [if your patch is applied to the wrong git tree, please drop us a note to
>
Hi ,
On 25 November 2016 at 22:32, kbuild test robot wrote:
> Hi Fu,
>
> [auto build test ERROR on pm/linux-next]
> [also build test ERROR on v4.9-rc6]
> [cannot apply to tip/timers/core next-20161125]
> [if your patch is applied to the wrong git tree, please drop us a note to
> help improve
Hi Fu,
[auto build test ERROR on pm/linux-next]
[also build test ERROR on v4.9-rc6]
[cannot apply to tip/timers/core next-20161125]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi Fu,
[auto build test ERROR on pm/linux-next]
[also build test ERROR on v4.9-rc6]
[cannot apply to tip/timers/core next-20161125]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
From: Fu Wei
Because arch_timer_needs_of_probing is only for booting with device-tree,
but arch_timer_common_init is a generic init call which shouldn't include
the FW-specific code. It's better to put arch_timer_needs_of_probing into
DT init function.
But for per-cpu timer,
From: Fu Wei
Because arch_timer_needs_of_probing is only for booting with device-tree,
but arch_timer_common_init is a generic init call which shouldn't include
the FW-specific code. It's better to put arch_timer_needs_of_probing into
DT init function.
But for per-cpu timer, the
14 matches
Mail list logo