linux-kernel - Re: [PATCH 48/60] microblaze_v4: headers simple files

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: <4641.7464-1541-432171441-1214572774@seznam.cz>
Date:	Fri, 27 Jun 2008 15:19:34 +0200 (CEST)
From:	Michal Simek <Monstr@...nam.cz>
To:	Adrian Bunk <bunk@...nel.org>
Cc:	Arnd Bergmann <arnd@...db.de>,
	linux-arch@...r.kernel.org, alan@...rguk.ukuu.org.uk,
	Michal Simek <monstr@...str.eu>,
	vapier.adi@...il.com, matthew@....cx,
	microblaze-uclinux@...e.uq.edu.au, linux-kernel@...r.kernel.org,
	drepper@...hat.com, linuxppc-dev@...abs.org, will.newton@...il.com,
	hpa@...or.com, John.Linn@...inx.com, john.williams@...alogix.com
Subject: Re: [PATCH 48/60] microblaze_v4: headers simple files - empty or redirect to asm-generic

Hi Adrian and Arnd,

>> > After all, it won't matter whether we'll unify resp. remove
>> > 22 or 23 files.
>> 
>> That wasn't my idea. The logic was that if one more file exists
>> in asm-generic that can be removed from the architectures,
>> we get 22 more files to remove without anyone having to look
>> at the big picture. When microblaze is in,
>
>Discussions of the "big picture" should be in an own thread, not as 
>part of a merge of a new architecture.
>
>I am not an architecture maintainer, but I do not like the way you want 
>to couple the microblaze merge with the move of stuff to asm-generic.
>
>They both make sense, but they are clearly separate issues.
>
>> I can compile a list
>> with asm-generic files that can be used to replace the architecture
>> specific files, so the arch maintainers can decide on their own
>> whether to clean their own stuff up or not.
>>...
>
>We need either all architectures changed or none at all - we do need the 
>arch headers to become more similar, not more different.
>
>And this is why we need an agreement _before_ an asm-generic header gets 
>added, not after it.

I moved some headers to asm-generic how Arnd recommended to me. The same style
is applied to of files. If you think that is good idea to start with new topic what is necessary to move
to asm-generic, I agree. For me is not hard to move these files back to asm-microblaze and then
someone can do big patch among all archs.
If you want to managed, please open new discussion about and cc me.

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