All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Viresh Kumar <viresh.kumar@linaro.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
	Linux-sh list <linux-sh@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Guenter Roeck <linux@roeck-us.net>
Subject: Re: Traceback in -next due to commit 'clockevents/drivers/sh_tmu: Migrate to new 'set-state' interfa
Date: Wed, 05 Aug 2015 12:38:16 +0000	[thread overview]
Message-ID: <55C203B8.4080206@linaro.org> (raw)
In-Reply-To: <20150803155155.GF21529@linux>

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 <geert+renesas@glider.be>
>
> Thanks. Daniel is back now and we should see this in linux-next soon.

Fixed and pushed in clockevents/next

-- 
  <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog


WARNING: multiple messages have this Message-ID (diff)
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Viresh Kumar <viresh.kumar@linaro.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
	Linux-sh list <linux-sh@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Guenter Roeck <linux@roeck-us.net>
Subject: Re: Traceback in -next due to commit 'clockevents/drivers/sh_tmu: Migrate to new 'set-state' interface'
Date: Wed, 05 Aug 2015 14:38:16 +0200	[thread overview]
Message-ID: <55C203B8.4080206@linaro.org> (raw)
In-Reply-To: <20150803155155.GF21529@linux>

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 <geert+renesas@glider.be>
>
> Thanks. Daniel is back now and we should see this in linux-next soon.

Fixed and pushed in clockevents/next

-- 
  <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog


  reply	other threads:[~2015-08-05 12:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-20 21:07 Traceback in -next due to commit 'clockevents/drivers/sh_tmu: Migrate to new 'set-state' interface' Guenter Roeck
2015-07-20 21:07 ` Guenter Roeck
2015-07-21  2:31 ` Viresh Kumar
2015-07-21  2:43   ` Traceback in -next due to commit 'clockevents/drivers/sh_tmu: Migrate to new 'set-state' interfa Viresh Kumar
2015-07-21  2:50   ` Guenter Roeck
2015-07-21  2:50     ` Traceback in -next due to commit 'clockevents/drivers/sh_tmu: Migrate to new 'set-state' interface' Guenter Roeck
2015-07-21  3:15     ` Viresh Kumar
2015-07-21  3:27       ` Traceback in -next due to commit 'clockevents/drivers/sh_tmu: Migrate to new 'set-state' interfa Viresh Kumar
2015-08-03 15:03     ` Geert Uytterhoeven
2015-08-03 15:03       ` Traceback in -next due to commit 'clockevents/drivers/sh_tmu: Migrate to new 'set-state' interface' Geert Uytterhoeven
2015-08-03 15:51       ` Viresh Kumar
2015-08-03 15:52         ` Traceback in -next due to commit 'clockevents/drivers/sh_tmu: Migrate to new 'set-state' interfa Viresh Kumar
2015-08-05 12:38         ` Daniel Lezcano [this message]
2015-08-05 12:38           ` Traceback in -next due to commit 'clockevents/drivers/sh_tmu: Migrate to new 'set-state' interface' Daniel Lezcano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55C203B8.4080206@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=geert@linux-m68k.org \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=viresh.kumar@linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.