linux-kernel - Re: linux-next:als tree build failure

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <4B618412.30704@cam.ac.uk>
Date:	Thu, 28 Jan 2010 12:33:22 +0000
From:	Jonathan Cameron <jic23@....ac.uk>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
CC:	Jean Delvare <khali@...ux-fr.org>, Zhang Rui <rui.zhang@...el.com>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next:als tree build failure

On 01/28/10 12:17, Stephen Rothwell wrote:
> Hi Jonathan, Jean,
> 
> On Thu, 28 Jan 2010 11:59:37 +0000 Jonathan Cameron <jic23@....ac.uk> wrote:
>>
>> It does make sense to keep these two steps separate.  Ah well, I guess any
>> work around would be a pretty terrible cludge.  I'll roll these two patches
>> back together and otherwise we will end up with something even less coherent.
> 
> OK, thanks guys.
> 
Everything should now be fixed in the als tree.  New version of the move commit
cleans out the i2c/chips directory and changes the i2c/Makefile and i2c/Kconfig
appropriately.  Only remaining related elements are the debug Kconfig option for
i2c/chips but that can definitely go through the i2c tree rather than als (if there
are no other users) and shouldn't break any builds.

Thanks,

Jonathan

--
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/