From: Tony Lindgren <tony@atomide.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: Jeroen Hofstee <linux-arm@myspectrum.nl>,
Tero Kristo <t-kristo@ti.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: dts: AM35xx: fix system control module clocks
Date: Mon, 1 Jun 2015 11:06:58 -0700 [thread overview]
Message-ID: <20150601180658.GB30984@atomide.com> (raw)
In-Reply-To: <20150601180429.GA30984@atomide.com>
* Tony Lindgren <tony@atomide.com> [150601 11:06]:
> * Paul Walmsley <paul@pwsan.com> [150601 10:45]:
> >
> > See for example the "Build warnings from toolchain", "Kernel warnings
> > during boot to userspace", "Kernel warnings during PM test", and "Obsolete
> > Kconfig symbols" sections here:
> >
> > http://www.pwsan.com/omap/testlogs/test_v4.1-rc6/20150601012139/README.txt
>
> OK somehow 3517evm is listed under "skip" there?
Oh I see you have two 3517 devices there, never mind.
Hmm now I'm wondering what the panda es warnings listed there are..
Tony
next prev parent reply other threads:[~2015-06-01 18:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-30 15:50 OMAP baseline test results for v4.1-rc5 Paul Walmsley
2015-05-30 15:56 ` Jeroen Hofstee
2015-05-31 22:15 ` Jeroen Hofstee
2015-06-01 5:49 ` Paul Walmsley
2015-06-01 15:29 ` Tero Kristo
2015-06-01 15:30 ` [PATCH] ARM: dts: AM35xx: fix system control module clocks Tero Kristo
2015-06-01 16:56 ` Jeroen Hofstee
2015-06-01 17:31 ` Tony Lindgren
2015-06-01 17:44 ` Paul Walmsley
2015-06-01 18:04 ` Tony Lindgren
2015-06-01 18:06 ` Tony Lindgren [this message]
2015-06-01 21:26 ` Paul Walmsley
2015-06-02 7:15 ` Tero Kristo
2015-06-01 21:21 ` Paul Walmsley
2015-06-01 18:04 ` Tero Kristo
2015-06-05 8:01 ` Jeroen Hofstee
2015-06-05 8:04 ` Jeroen Hofstee
2015-06-07 9:41 ` Jeroen Hofstee
2015-06-07 19:56 ` Paul Walmsley
2015-06-08 2:38 ` Paul Walmsley
2015-06-08 22:00 ` Jeroen Hofstee
2015-06-08 21:43 ` Jeroen Hofstee
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=20150601180658.GB30984@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm@myspectrum.nl \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=t-kristo@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).