linux-kernel - Re: [PATCH v5 00/11] drivers: cacheinfo support

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 for Android: free password hash cracker in your pocket

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

Message-ID: <544626AD.403@arm.com>
Date:	Tue, 21 Oct 2014 10:26:05 +0100
From:	Sudeep Holla <sudeep.holla@....com>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
CC:	Sudeep Holla <sudeep.holla@....com>,
	LKML <linux-kernel@...r.kernel.org>,
	Heiko Carstens <heiko.carstens@...ibm.com>,
	Lorenzo Pieralisi <Lorenzo.Pieralisi@....com>
Subject: Re: [PATCH v5 00/11] drivers: cacheinfo support

Hi Greg,

On 20/10/14 19:49, Greg Kroah-Hartman wrote:
> On Mon, Oct 20, 2014 at 07:46:19PM +0100, Sudeep Holla wrote:
>> Hi Greg,
>>
>> On 30/09/14 14:48, Sudeep Holla wrote:
>>> This series adds a generic cacheinfo support similar to topology. The
>>> implementation is based on x86 cacheinfo support. Currently x86, powerpc,
>>> ia64 and s390 have their own implementations. While adding similar support
>>> to ARM and ARM64, here is the attempt to make it generic quite similar to
>>> topology info support. It also adds the missing ABI documentation for
>>> the cacheinfo sysfs which is already being used.
>>>
>>> It moves all the existing different implementations on x86, ia64, powerpc
>>> and s390 to use the generic cacheinfo infrastructure introduced here.
>>> These changes on non-ARM platforms are only compile tested and tested on x86.
>>>
>>> This series also adds support for ARM and ARM64 architectures based on
>>> the generic support.
>>>
>>> The code can be fetched from:
>>>   git://linux-arm.org/linux-skn cacheinfo
>>>
>>
>> I am hoping to target this for v3.19 if possible, it would be good if
>> you can review and provide feedback.
>
> 3.18-rc1 just came out a few _hours_ ago, and now we can start worrying
> about what goes into 3.19.  I have 1257 emails in my "to-review" queue
> for 3.19, please give me a chance to catch up in a few weeks to get to
> this code.
>

I completely understand and I am sorry if that was a noise.
I just wanted to ensure it's not lost, thanks for letting me know it's
in your list.

Regards,
Sudeep

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