On 08/03/2015 05:51 PM, Viresh Kumar wrote:
On 03-08-15, 17:03, Geert Uytterhoeven wrote:
I'm seeing the same WARNING on ARM (r8a7740/armadillo), and it's fixed by
your patch.
Tested-by: Geert Uytterhoeven
Thanks. Daniel is back now and we should see this in linux-next soon.
Fixed and push
On 03-08-15, 17:03, Geert Uytterhoeven wrote:
> I'm seeing the same WARNING on ARM (r8a7740/armadillo), and it's fixed by
> your patch.
>
> Tested-by: Geert Uytterhoeven
Thanks. Daniel is back now and we should see this in linux-next soon.
--
viresh
--
To unsubscribe from this list: send the l
Hi Viresh,
On Tue, Jul 21, 2015 at 4:50 AM, Guenter Roeck wrote:
> On 07/20/2015 07:31 PM, Viresh Kumar wrote:
>> On 20-07-15, 14:07, Guenter Roeck wrote:
>>> Commit 991a7f4970ed1 ("clockevents/drivers/sh_tmu: Migrate to new
>>> 'set-state' interface")
>>> in -next causes the following traceback.
On 20-07-15, 19:50, Guenter Roeck wrote:
> This patch fixes the problem.
Thanks for doing this quickly. Daniel isn't around right now and may
take some time to get this commited.
--
viresh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majo
On 07/20/2015 07:31 PM, Viresh Kumar wrote:
On 20-07-15, 14:07, Guenter Roeck wrote:
Hi,
Commit 991a7f4970ed1 ("clockevents/drivers/sh_tmu: Migrate to new 'set-state'
interface")
in -next causes the following traceback. This is seen with qemu runs for the sh
target.
[ cut here ]-
On 20-07-15, 14:07, Guenter Roeck wrote:
> Hi,
>
> Commit 991a7f4970ed1 ("clockevents/drivers/sh_tmu: Migrate to new 'set-state'
> interface")
> in -next causes the following traceback. This is seen with qemu runs for the
> sh target.
>
> [ cut here ]
> WARNING: at drive
Hi,
Commit 991a7f4970ed1 ("clockevents/drivers/sh_tmu: Migrate to new 'set-state'
interface")
in -next causes the following traceback. This is seen with qemu runs for the sh
target.
[ cut here ]
WARNING: at drivers/clocksource/sh_tmu.c:202
Modules linked in:
CPU: 0 PID
7 matches
Mail list logo