Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753971AbbEMIds (ORCPT ); Wed, 13 May 2015 04:33:48 -0400 Received: from mail-wi0-f180.google.com ([209.85.212.180]:38024 "EHLO mail-wi0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752925AbbEMIdp (ORCPT ); Wed, 13 May 2015 04:33:45 -0400 MIME-Version: 1.0 From: Valentin Rothberg Date: Wed, 13 May 2015 10:33:13 +0200 Message-ID: Subject: h8300: device tree: undefined CONFIG_EDOSK2674 To: ysato@users.sourceforge.jp Cc: dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com, ijc+devicetree@hellion.org.uk, galak@codeaurora.org, devicetree@vger.kernel.org, uclinux-h8-devel@lists.sourceforge.jp, linux-kernel@vger.kernel.org, Paul Bolle , Andreas Ruprecht , hengelein Stefan Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 770 Lines: 21 Hi Yoshinori, your commit 5befaa907481 ("h8300: devicetree source") is in today's linux-next tree (i.e., next-20150513) and adds the following line: +dtb-$(CONFIG_EDOSK2674) := edosk2674.dtb EDOSK2674 is not defined in Kconfig so that the device tree source won't be touched. Some grepping indicates that it's just a typo and 'H8S_EDOSK2674' may be the correct option. Is that right? I detected this issue with scripts/checkkconfigsymbols.py by diffing yesterday's and today's linux-next tree. Kind regards, Valentin -- 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/