From: sre@ring0.de (Sebastian Reichel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP2+: Warn about deprecated legacy booting mode
Date: Wed, 29 Oct 2014 19:59:57 +0100 [thread overview]
Message-ID: <20141029185957.GA3723@earth.universe> (raw)
In-Reply-To: <5450EEE7.8070801@ti.com>
Hi,
On Wed, Oct 29, 2014 at 08:43:03AM -0500, Nishanth Menon wrote:
> On 10/28/2014 05:12 PM, Tony Lindgren wrote:
> > * Aaro Koskinen <aaro.koskinen@iki.fi> [141027 16:03]:
> >> Hi,
> >>
> >> On Mon, Oct 27, 2014 at 01:00:09PM -0700, Tony Lindgren wrote:
> >>> +
> >>> + if (!of_have_populated_dt())
> >>> + pr_warn("WARNING: legacy booting deprecated, please update to boot with .dts\n");
> >>> +
> >>
> >> Maybe use WARN so that the warning is more verbose and kernel gets tainted?
> >
> > Well I was hoping to avoid annoying people with the trace.
> > But can do that if people prefer that, what do others think?
> >
>
> WARN is better and eye catchy. Also, could we add information on when
> the support will be removed since we call it deprecated?
I also think, that more eye catchy is better.
Apart from that I wonder if we should drop support on a
board-by-board basis and then drop omap3 support completly once all
boards have been dropped.
-- Sebastian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20141029/5168a2d0/attachment.sig>
next prev parent reply other threads:[~2014-10-29 18:59 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 20:00 [PATCH] ARM: OMAP2+: Warn about deprecated legacy booting mode Tony Lindgren
2014-10-27 23:01 ` Aaro Koskinen
2014-10-28 22:12 ` Tony Lindgren
2014-10-29 13:43 ` Nishanth Menon
2014-10-29 18:59 ` Sebastian Reichel [this message]
2014-10-29 19:39 ` Tony Lindgren
2014-10-29 21:45 ` Nishanth Menon
2014-10-29 22:15 ` Tony Lindgren
2014-10-29 22:31 ` Aaro Koskinen
2014-10-30 13:55 ` Nishanth Menon
2014-10-29 23:07 ` Sebastian Reichel
2014-10-29 23:11 ` Aaro Koskinen
2014-10-29 23:54 ` Javier Martinez Canillas
2014-11-26 17:28 ` Pavel Machek
2014-11-26 18:19 ` Tony Lindgren
2014-11-26 18:57 ` Pali Rohár
2014-11-26 19:10 ` Tony Lindgren
2014-11-26 19:22 ` Pali Rohár
2014-11-26 20:08 ` Tony Lindgren
2014-11-26 23:01 ` Pali Rohár
2014-11-26 23:14 ` Tony Lindgren
2014-11-26 23:38 ` Pali Rohár
2014-11-27 1:12 ` Tony Lindgren
2014-11-27 11:32 ` Pali Rohár
2014-11-28 20:27 ` Tony Lindgren
2014-11-28 21:41 ` Pali Rohár
2014-11-28 22:24 ` Tony Lindgren
2014-11-28 22:42 ` Pali Rohár
2014-12-04 18:34 ` Pali Rohár
2014-12-04 18:40 ` Tony Lindgren
2014-12-04 19:01 ` Pali Rohár
2014-11-28 22:26 ` Aaro Koskinen
2014-11-28 22:43 ` Pali Rohár
2014-11-28 22:41 ` Aaro Koskinen
2014-11-28 22:49 ` Pali Rohár
2014-11-28 22:54 ` Aaro Koskinen
2014-12-02 21:28 ` Pali Rohár
2014-12-03 16:52 ` Pavel Machek
2014-11-27 11:18 ` Pavel Machek
2014-10-31 19:30 ` Russell King - ARM Linux
2014-10-31 21:13 ` Tony Lindgren
2014-10-31 22:12 ` Tony Lindgren
2014-10-31 22:33 ` Russell King - ARM Linux
2014-10-31 23:37 ` Tony Lindgren
2014-11-01 0:44 ` Russell King - ARM Linux
2014-11-01 21:57 ` Tony Lindgren
2014-11-02 18:15 ` Tony Lindgren
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=20141029185957.GA3723@earth.universe \
--to=sre@ring0.de \
--cc=linux-arm-kernel@lists.infradead.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 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).