From: Robert ABEL <rabel@cit-ec.uni-bielefeld.de>
To: akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: of: dynamic: resource: add WARN in release_resource for DT overlays
Date: Thu, 30 Jul 2015 15:17:16 +0200 [thread overview]
Message-ID: <1438262237-30889-1-git-send-email-rabel@cit-ec.uni-bielefeld.de> (raw)
In-Reply-To: <[PATCH v3 0/7] Introducing (yet again) Device Tree Overlays>
This patch prevents a kernel OOPS when removing a DT overlay containing
nodes with reg properties. release_resources is called for these nodes.
However, the resource structs were never initialized, hence the kernel OOPS.
This is obviously a stopgap measure until a proper solution is coded, see [1].
[1]: https://lkml.org/lkml/2014/4/17/359
next parent reply other threads:[~2015-07-30 13:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <[PATCH v3 0/7] Introducing (yet again) Device Tree Overlays>
2015-07-30 13:17 ` Robert ABEL [this message]
2015-07-30 13:17 ` [PATCH] of: resource: add WARN for invalid release_resource calls Robert ABEL
2015-08-05 21:04 ` of: dynamic: resource: add WARN in release_resource for DT overlays Andrew Morton
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=1438262237-30889-1-git-send-email-rabel@cit-ec.uni-bielefeld.de \
--to=rabel@cit-ec.uni-bielefeld.de \
--cc=akpm@linux-foundation.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@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 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).