Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752612AbbDEO7a (ORCPT ); Sun, 5 Apr 2015 10:59:30 -0400 Received: from michel.telenet-ops.be ([195.130.137.88]:35863 "EHLO michel.telenet-ops.be" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752136AbbDEO73 (ORCPT ); Sun, 5 Apr 2015 10:59:29 -0400 From: Geert Uytterhoeven To: Grant Likely , Rob Herring , Arnd Bergmann Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Geert Uytterhoeven Subject: [PATCH 0/3] of: Increase compile coverage Date: Sun, 5 Apr 2015 16:59:22 +0200 Message-Id: <1428245965-19618-1-git-send-email-geert@linux-m68k.org> X-Mailer: git-send-email 1.9.1 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1279 Lines: 38 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/