devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Grant Likely <grant.likely@linaro.org>,
	Rob Herring <robh+dt@kernel.org>, Arnd Bergmann <arnd@arndb.de>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	Geert Uytterhoeven <geert@linux-m68k.org>
Subject: [PATCH 0/3] of: Increase compile coverage
Date: Sun,  5 Apr 2015 16:59:22 +0200	[thread overview]
Message-ID: <1428245965-19618-1-git-send-email-geert@linux-m68k.org> (raw)

	Hi,

Currently the OF configuration symbol is explicitly selected on
architectures that support device trees and/or Open Firmware.
However, there's no technical reason to limit the device tree
infrastructure to these architectures.

Hence this series allows to enable OF when compile testing, to increase
compile coverage. It also fixes the fallout I encountered when IRQ
domain support is not enabled.

Geert Uytterhoeven (3):
  of: Allow OF to be enabled if COMPILE_TEST to increase coverage
  of: OF_IRQ should depend on IRQ_DOMAIN
  of: Add dummy of_irq_to_resource_table() for IRQ_OF=n

 drivers/of/Kconfig     | 8 ++++++--
 include/linux/of_irq.h | 9 +++++++--
 2 files changed, 13 insertions(+), 4 deletions(-)

-- 
1.9.1

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

             reply	other threads:[~2015-04-05 14:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-05 14:59 Geert Uytterhoeven [this message]
     [not found] ` <1428245965-19618-1-git-send-email-geert-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org>
2015-04-05 14:59   ` [PATCH 1/3] of: Allow OF to be enabled if COMPILE_TEST to increase coverage Geert Uytterhoeven
     [not found]     ` <1428245965-19618-2-git-send-email-geert-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org>
2015-04-06 13:13       ` Rob Herring
     [not found]         ` <CAL_JsqLQrNEpqWnqP4uDV0x87wERLC50FO-06fYBwLbyYsChpQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-04-23 12:03           ` Pantelis Antoniou
     [not found]             ` <0C5158C3-2BD3-4EC6-B1AC-B669F30B4C34-OWPKS81ov/FWk0Htik3J/w@public.gmane.org>
2015-04-23 18:22               ` Rob Herring
2015-04-23 18:28                 ` Pantelis Antoniou
2015-04-05 14:59 ` [PATCH 2/3] of: OF_IRQ should depend on IRQ_DOMAIN Geert Uytterhoeven
2015-04-06 14:40   ` Arnd Bergmann
2015-04-06 15:26     ` Rob Herring
2015-04-06 15:26     ` Geert Uytterhoeven
2015-04-06 21:39       ` Arnd Bergmann
     [not found]   ` <1428245965-19618-3-git-send-email-geert-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org>
2015-04-15 12:54     ` Rob Herring
2015-04-05 14:59 ` [PATCH 3/3] of: Add dummy of_irq_to_resource_table() for IRQ_OF=n Geert Uytterhoeven
     [not found]   ` <1428245965-19618-4-git-send-email-geert-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org>
2015-04-15 12:54     ` 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=1428245965-19618-1-git-send-email-geert@linux-m68k.org \
    --to=geert@linux-m68k.org \
    --cc=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=grant.likely@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@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).