From: Nishanth Menon <nm@ti.com>
To: Mark Brown <broonie@kernel.org>
Cc: Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org, linux-next@vger.kernel.org
Subject: Re: LDP: next-20150402: twl4030 regression?
Date: Mon, 06 Apr 2015 08:53:36 -0500 [thread overview]
Message-ID: <55228FE0.2040702@ti.com> (raw)
In-Reply-To: <20150406134541.GE6023@sirena.org.uk>
On 04/06/2015 08:45 AM, Mark Brown wrote:
> On Mon, Apr 06, 2015 at 08:21:49AM -0500, Nishanth Menon wrote:
>
>> https://github.com/nmenon/kernel-test-logs/blob/next-20150401/omap2plus_defconfig/ldp.txt
>> looks clean, but
>
>> https://github.com/nmenon/kernel-test-logs/blob/next-20150402/omap2plus_defconfig/ldp.txt#L488
>> seems to have picked up a regression in the regulator driver.
>
> Please provide actual bug reports if you're trying to report something -
Apologies, I should have been a little more clear.
> at least a description of the problem you're seeing and some attempt at
Test was a simple boot test. There seems to be a lockdep reported at the
very least in the log provided (see
https://github.com/nmenon/kernel-test-logs/blob/next-20150402/omap2plus_defconfig/ldp.txt#L488
).
> analysis. For example say what the test was, and if there's logs paste
> the relevant section into the e-mail. Just randomly pasting a couple of
> web links in and saying "there's a problem" isn't helpful.
Not sure if folks have already seen this or not - clicking the link
should show the lockdep report straight out of the box.. I am thinking
that is a problem... but I might be subjective here :)
>
> Please also CC people responsible for relevant drivers and systems.
>
Only quick change I could see was in regulator core, Will try to dig
more at this later today. I dont see the filesystem mounted either, but
that could be something else.
--
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: LDP: next-20150402: twl4030 regression?
Date: Mon, 06 Apr 2015 08:53:36 -0500 [thread overview]
Message-ID: <55228FE0.2040702@ti.com> (raw)
In-Reply-To: <20150406134541.GE6023@sirena.org.uk>
On 04/06/2015 08:45 AM, Mark Brown wrote:
> On Mon, Apr 06, 2015 at 08:21:49AM -0500, Nishanth Menon wrote:
>
>> https://github.com/nmenon/kernel-test-logs/blob/next-20150401/omap2plus_defconfig/ldp.txt
>> looks clean, but
>
>> https://github.com/nmenon/kernel-test-logs/blob/next-20150402/omap2plus_defconfig/ldp.txt#L488
>> seems to have picked up a regression in the regulator driver.
>
> Please provide actual bug reports if you're trying to report something -
Apologies, I should have been a little more clear.
> at least a description of the problem you're seeing and some attempt at
Test was a simple boot test. There seems to be a lockdep reported at the
very least in the log provided (see
https://github.com/nmenon/kernel-test-logs/blob/next-20150402/omap2plus_defconfig/ldp.txt#L488
).
> analysis. For example say what the test was, and if there's logs paste
> the relevant section into the e-mail. Just randomly pasting a couple of
> web links in and saying "there's a problem" isn't helpful.
Not sure if folks have already seen this or not - clicking the link
should show the lockdep report straight out of the box.. I am thinking
that is a problem... but I might be subjective here :)
>
> Please also CC people responsible for relevant drivers and systems.
>
Only quick change I could see was in regulator core, Will try to dig
more at this later today. I dont see the filesystem mounted either, but
that could be something else.
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2015-04-06 13:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-06 13:21 LDP: next-20150402: twl4030 regression? Nishanth Menon
2015-04-06 13:21 ` Nishanth Menon
2015-04-06 13:45 ` Mark Brown
2015-04-06 13:45 ` Mark Brown
2015-04-06 13:53 ` Nishanth Menon [this message]
2015-04-06 13:53 ` Nishanth Menon
2015-04-06 13:58 ` Russell King - ARM Linux
2015-04-06 13:58 ` Russell King - ARM Linux
2015-04-06 15:01 ` Mark Brown
2015-04-06 15:01 ` Mark Brown
2015-04-06 15:17 ` Nishanth Menon
2015-04-06 15:17 ` Nishanth Menon
2015-04-06 15:27 ` Felipe Balbi
2015-04-06 15:27 ` Felipe Balbi
2015-04-06 18:45 ` Nishanth Menon
2015-04-06 18:45 ` Nishanth Menon
2015-04-08 16:35 ` Felipe Balbi
2015-04-08 16:35 ` Felipe Balbi
2015-04-08 21:46 ` Stephen Rothwell
2015-04-08 21:46 ` Stephen Rothwell
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=55228FE0.2040702@ti.com \
--to=nm@ti.com \
--cc=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-omap@vger.kernel.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.