From: Yoshinori Sato <ysato@users.sourceforge.jp>
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>
Subject: Re: h8300: device tree: undefined CONFIG_EDOSK2674
Date: Wed, 13 May 2015 22:48:13 +0900 [thread overview]
Message-ID: <87zj58bnc2.wl-ysato@users.sourceforge.jp> (raw)
In-Reply-To: <CAD3Xx4+4E_ueLzP9Jn+ZcxkbBbAEby=gyH-bUVKo_5WKpB-K-A@mail.gmail.com>
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>
prev parent reply other threads:[~2015-05-13 13:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 8:33 h8300: device tree: undefined CONFIG_EDOSK2674 Valentin Rothberg
2015-05-13 13:48 ` Yoshinori Sato [this message]
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=87zj58bnc2.wl-ysato@users.sourceforge.jp \
--to=ysato@users.sourceforge.jp \
--cc=andreas.ruprecht@fau.de \
--cc=devicetree@vger.kernel.org \
--cc=dt@kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=pebolle@tiscali.nl \
--cc=stefan.hengelein@fau.de \
--cc=uclinux-h8-devel@lists.sourceforge.jp \
--cc=valentinrothberg@gmail.com \
/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