From mboxrd@z Thu Jan  1 00:00:00 1970
From: Yoshinori Sato <ysato@users.sourceforge.jp>
Subject: Re: h8300: device tree: undefined CONFIG_EDOSK2674
Date: Wed, 13 May 2015 22:48:13 +0900
Message-ID: <87zj58bnc2.wl-ysato@users.sourceforge.jp>
References: <CAD3Xx4+4E_ueLzP9Jn+ZcxkbBbAEby=gyH-bUVKo_5WKpB-K-A@mail.gmail.com>
Mime-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Return-path: <linux-kernel-owner@vger.kernel.org>
In-Reply-To: <CAD3Xx4+4E_ueLzP9Jn+ZcxkbBbAEby=gyH-bUVKo_5WKpB-K-A@mail.gmail.com>
Sender: linux-kernel-owner@vger.kernel.org
To: Valentin Rothberg <valentinrothberg@gmail.com>
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 <pebolle@tiscali.nl>, Andreas Ruprecht <andreas.ruprecht@fau.de>, hengelein Stefan <stefan.hengelein@fau.de>
List-Id: devicetree@vger.kernel.org

At Wed, 13 May 2015 10:33:13 +0200,
Valentin Rothberg wrote:
> 
> 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

Yes.
CONFIG_H8S_EDOSK2674 is correct.

Thanks report.

-- 
Yoshinori Sato
<ysato@users.sourceforge.jp>