All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>,
	Tomasz Figa <tomasz.figa@gmail.com>
Cc: Kevin Hilman <khilman@linaro.org>,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	linux-omap <linux-omap@vger.kernel.org>,
	"tony@atomide.com" <tony@atomide.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	linux-next <linux-next@vger.kernel.org>,
	linux-samsung-soc <linux-samsung-soc@vger.kernel.org>
Subject: Re: regression: OMAP4 (next-20141204) (bisect to: ARM: 8208/1: l2c: Refactor the driver to use commit-like)
Date: Mon, 8 Dec 2014 07:54:08 -0600	[thread overview]
Message-ID: <5485AD80.1050008@ti.com> (raw)
In-Reply-To: <20141208122235.GC11502@n2100.arm.linux.org.uk>

On 12/08/2014 06:22 AM, Russell King - ARM Linux wrote:
> On Mon, Dec 08, 2014 at 08:54:18PM +0900, Tomasz Figa wrote:
>> 2014-12-06 1:23 GMT+09:00 Russell King - ARM Linux <linux@arm.linux.org.uk>:
>>> Given where we are in the cycle (-final likely this weekend) the only
>>> thing we can do right now is to drop the patch set; exynos (and mvebu)
>>> will have to wait another cycle until this patch set (hopefully in a
>>> revised form) can be merged.
>>
>> Or a fix could be queued on top of this. Since (I believe) this series
>> has been queued for 3.19, we have 6 or 7 RC releases ahead, which
>> could be used for the purpose of fixing things (as they are supposed
>> to?).
> 
> They were merged on 27th November, so they would've been in linux-next
> from about last Monday.  Nishanth reported a failure on Friday, the

For what ever it is worth, the l2c changes actually appeared on
Thursday CST (next-20141204). Found the regression against
next-20141203 tag and it took me a day to track it down (after looking
at a few other regressions as well)..

Anyways...

-- 
Regards,
Nishanth Menon

WARNING: multiple messages have this Message-ID (diff)
From: nm@ti.com (Nishanth Menon)
To: linux-arm-kernel@lists.infradead.org
Subject: regression: OMAP4 (next-20141204) (bisect to: ARM: 8208/1: l2c: Refactor the driver to use commit-like)
Date: Mon, 8 Dec 2014 07:54:08 -0600	[thread overview]
Message-ID: <5485AD80.1050008@ti.com> (raw)
In-Reply-To: <20141208122235.GC11502@n2100.arm.linux.org.uk>

On 12/08/2014 06:22 AM, Russell King - ARM Linux wrote:
> On Mon, Dec 08, 2014 at 08:54:18PM +0900, Tomasz Figa wrote:
>> 2014-12-06 1:23 GMT+09:00 Russell King - ARM Linux <linux@arm.linux.org.uk>:
>>> Given where we are in the cycle (-final likely this weekend) the only
>>> thing we can do right now is to drop the patch set; exynos (and mvebu)
>>> will have to wait another cycle until this patch set (hopefully in a
>>> revised form) can be merged.
>>
>> Or a fix could be queued on top of this. Since (I believe) this series
>> has been queued for 3.19, we have 6 or 7 RC releases ahead, which
>> could be used for the purpose of fixing things (as they are supposed
>> to?).
> 
> They were merged on 27th November, so they would've been in linux-next
> from about last Monday.  Nishanth reported a failure on Friday, the

For what ever it is worth, the l2c changes actually appeared on
Thursday CST (next-20141204). Found the regression against
next-20141203 tag and it took me a day to track it down (after looking
at a few other regressions as well)..

Anyways...

-- 
Regards,
Nishanth Menon

  reply	other threads:[~2014-12-08 13:54 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-05 16:10 regression: OMAP4 (next-20141204) (bisect to: ARM: 8208/1: l2c: Refactor the driver to use commit-like) Nishanth Menon
2014-12-05 16:10 ` Nishanth Menon
2014-12-05 16:13 ` Nishanth Menon
2014-12-05 16:13   ` Nishanth Menon
2014-12-05 16:23   ` Russell King - ARM Linux
2014-12-05 16:23     ` Russell King - ARM Linux
2014-12-08 11:54     ` Tomasz Figa
2014-12-08 11:54       ` Tomasz Figa
2014-12-08 12:22       ` Russell King - ARM Linux
2014-12-08 12:22         ` Russell King - ARM Linux
2014-12-08 13:54         ` Nishanth Menon [this message]
2014-12-08 13:54           ` Nishanth Menon
2014-12-08 15:11           ` Russell King - ARM Linux
2014-12-08 15:11             ` Russell King - ARM Linux
2014-12-09 16:57   ` Nishanth Menon
2014-12-09 16:57     ` Nishanth Menon
2014-12-10  9:42     ` Marek Szyprowski
2014-12-10  9:42       ` Marek Szyprowski
2014-12-11  9:29       ` Russell King - ARM Linux
2014-12-11  9:29         ` Russell King - ARM Linux
2014-12-11 10:42         ` Marek Szyprowski
2014-12-11 10:42           ` Marek Szyprowski
2014-12-22 17:04           ` Russell King - ARM Linux
2014-12-22 17:04             ` Russell King - ARM Linux
2014-12-22 17:08             ` Tony Lindgren
2014-12-22 17:08               ` Tony Lindgren
2014-12-22 17:12             ` Nishanth Menon
2014-12-22 17:12               ` Nishanth Menon
2014-12-22 17:28               ` Russell King - ARM Linux
2014-12-22 17:28                 ` Russell King - ARM Linux
2014-12-23 11:00                 ` Marek Szyprowski
2014-12-23 11:00                   ` Marek Szyprowski
2014-12-23 11:10                   ` Russell King - ARM Linux
2014-12-23 11:10                     ` Russell King - ARM Linux
2014-12-23 16:05                     ` Nishanth Menon
2014-12-23 16:05                       ` Nishanth Menon

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=5485AD80.1050008@ti.com \
    --to=nm@ti.com \
    --cc=khilman@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=m.szyprowski@samsung.com \
    --cc=tomasz.figa@gmail.com \
    --cc=tony@atomide.com \
    /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.