linux-kernel - Re: [PATCH 54/56] x86: Remove void casts

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]

Date:	Wed, 08 Apr 2009 15:59:43 +0100
From:	Jack Stone <jwjstone@...tmail.fm>
To:	Ingo Molnar <mingo@...e.hu>
CC:	Bert Wesarg <bert.wesarg@...glemail.com>,
	linux-kernel@...r.kernel.org, jeff@...zik.org,
	kernel-janitors@...r.kernel.org
Subject: Re: [PATCH 54/56] x86: Remove void casts

Ingo Molnar wrote:
> * Jack Stone <jwjstone@...tmail.fm> wrote:
>
>   
>> Ingo Molnar wrote:
>>     
>>> No, i mean, this approach should be changed, and i dont think any 
>>> type cast change should go via any trivial tree. It's easy to mess 
>>> it up. Please submit them to the maintainer trees
>>>       
>> Ok. I'll try and find appropriate CCs. I'm going out shortly so it 
>> might take me a while.
>>     
>
> Since you do many such patches it might make sense to script up a 
> "who maintains what" kind of script - and share that script with 
> lkml.
>
> I have this silly little script:
>
>   git log $@ | grep Signed-off-by: |
>    cut -d: -f2 | cut -d\< -f1 |
>     sort | uniq -c | sort -n
>
> To find out any recent parties that touches a particular file. But 
> it would be nice to somehow automate the pickup of mailing-list 
> addresses from MAINTAINERS for example. We've literally got hundreds 
> of email lists there.
>
> It is not trivial to do though :-)
>   
It would be useful. The main problem is working out what files belong to
what MAINTAINERS entries.

I'll see what I can cook up.

Thanks,

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