linux-kernel - Re: staging: remove i2o subsystem: some leftovers

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]

Message-ID: <CAD3Xx4KomPcA61fYnoy2zPeAhMupUxLGaJBRzehtBrZ4gBByiw@mail.gmail.com>
Date:	Thu, 14 May 2015 14:58:14 +0200
From:	Valentin Rothberg <valentinrothberg@...il.com>
To:	Greg KH <gregkh@...uxfoundation.org>
Cc:	devel@...verdev.osuosl.org, Paul Bolle <pebolle@...cali.nl>,
	Andreas Ruprecht <andreas.ruprecht@....de>,
	linux-kernel@...r.kernel.org,
	hengelein Stefan <stefan.hengelein@....de>,
	alan@...ux.intel.com
Subject: Re: staging: remove i2o subsystem: some leftovers

Hi Greg,

On Thu, May 14, 2015 at 2:54 PM, Greg KH <gregkh@...uxfoundation.org> wrote:
> On Thu, May 14, 2015 at 01:37:04PM +0200, Valentin Rothberg wrote:
>> Hi Greg,
>>
>> your commit 4a72a7af462d ("staging: remove i2o subsystem") is in
>> today's linux-next tree (i.e., next-20150514) and it removes the
>> menuconfig I2O, but leaves the following line untouched:
>>
>> drivers/Makefile:101:obj-$(CONFIG_I2O)          += message/
>>
>> Can this line and the folder be removed or should it depend on another option?
>
> The folder can't be removed (other things are in there), but this line
> can.  Can you send me a patch removing it so that you get the correct
> credit for finding this?  :)

Sure.  I will prepare a patch that removes this line.

Kind regards,
 Valentin

> thanks,
>
> greg k-h
--
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/