From: Peter Crosthwaite <peter.crosthwaite-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>
To: grant-likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org
Subject: [PATCH v1 0/2] of: irq: Ignore disabled interrupt controllers
Date: Wed, 27 Nov 2013 23:26:11 -0800 [thread overview]
Message-ID: <cover.1385623064.git.peter.crosthwaite@xilinx.com> (raw)
Hi All,
These two patches support the case where an interrupt controller is
marked as disabled. Patch 1 fixed the dts interrupt-map search logic to
ignore disabled interrupt controllers. Patch 2 stops disabled interrupt
controllers getting probed.
Peter Crosthwaite (2):
of: irq: Ignore disabled intc's when searching map
of: irq: Ignore disabled interrupt controllers
drivers/of/irq.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
--
1.8.4.4
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2013-11-28 7:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-28 7:26 Peter Crosthwaite [this message]
2013-11-28 7:26 ` [PATCH v1 2/2] of: irq: Ignore disabled interrupt controllers Peter Crosthwaite
[not found] ` <cover.1385623064.git.peter.crosthwaite-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>
2013-11-28 7:26 ` [PATCH v1 1/2] of: irq: Ignore disabled intc's when searching map Peter Crosthwaite
[not found] ` <ee3c0c716da8f1b1146d8829bc5184fbf1c3ead2.1385623064.git.peter.crosthwaite-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>
2013-12-04 4:42 ` Peter Crosthwaite
2013-12-04 19:24 ` [PATCH v1 0/2] of: irq: Ignore disabled interrupt controllers Rob Herring
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=cover.1385623064.git.peter.crosthwaite@xilinx.com \
--to=peter.crosthwaite-gjffaj9ahvfqt0dzr+alfa@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=grant-likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.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).