lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 13 May 2015 22:48:13 +0900 From: Yoshinori Sato <ysato@...rs.sourceforge.jp> To: Valentin Rothberg <valentinrothberg@...il.com> Cc: dt@...nel.org, pawel.moll@....com, mark.rutland@....com, ijc+devicetree@...lion.org.uk, galak@...eaurora.org, devicetree@...r.kernel.org, uclinux-h8-devel@...ts.sourceforge.jp, linux-kernel@...r.kernel.org, Paul Bolle <pebolle@...cali.nl>, Andreas Ruprecht <andreas.ruprecht@....de>, hengelein Stefan <stefan.hengelein@....de> Subject: Re: h8300: device tree: undefined CONFIG_EDOSK2674 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@...rs.sourceforge.jp> -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists