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-prev] [day] [month] [year] [list]
Date:	Tue, 5 Apr 2016 19:33:22 +0200
From:	Lars-Peter Clausen <lars@...afoo.de>
To:	Valentin Rothberg <valentinrothberg@...il.com>
Cc:	jic23@...nel.org, LKML <linux-kernel@...r.kernel.org>,
	Andreas Ziegler <ziegler@...fau.de>
Subject: Re: staging:iio:adis162** cleanup

On 04/05/2016 08:03 AM, Valentin Rothberg wrote:
> 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.

Hi,

Sorry, I totally overlooked those. Please go ahead and remove those #if blocks.

Thanks,
- Lars

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ