linux-kernel - staging:iio:adis162** cleanup

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20160405060312.GA2094@doudou.informatik.uni-erlangen.de>
Date:	Tue, 5 Apr 2016 08:03:12 +0200
From:	Valentin Rothberg <valentinrothberg@...il.com>
To:	lars@...afoo.de
Cc:	jic23@...nel.org, LKML <linux-kernel@...r.kernel.org>,
	Andreas Ziegler <ziegler@...fau.de>
Subject: staging:iio:adis162** cleanup

Hi Lars-Peter,

both of your commits 88ae3aedb8ec ("staging:iio:adis16204: Remove
adis16204 driver") and 2bcdb3f2e05f ("staging:iio:adis16220: Remove
adis16220 driver") have shown up in today's linux-next.

The corresponding Kconfig options are still referenced in the __initdata
struct in arch/blackfin/mach-bf537/boards/stamp.c.  Shall I send a
trivial patch removing the two #if's or do you prefer to keep them?

I detected the issue with scripts/checkkconfigsymbols.py by diffing
yesterday's and today's linux-next.

Best regards,
 Valentin