linux-kernel - Re: [PATCH 0/5, resend] x86: use asm-generic headers where possible

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

Message-Id: <1245393058.2463.13.camel@ht.satnam>
Date:	Fri, 19 Jun 2009 12:00:58 +0530
From:	Jaswinder Singh Rajput <jaswinder@...nel.org>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	Ingo Molnar <mingo@...e.hu>, x86 maintainers <x86@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH 0/5, resend] x86: use asm-generic headers where possible

Hello Arnd,

On Thu, 2009-06-18 at 21:48 +0200, Arnd Bergmann wrote:
> I did not get any feedback on this the last time I sent it,
> but now these patches actually apply to the mainline kernel
> so it's possible to apply them.
> 
> I've split the series up into five patches for easier review.
> Each step should show clearly that no semantic changes are
> introduced, with the exception of termios.h, which was
> discussed earlier.
> 

Nice work.

IMHO, if you provide above steps for each file for all architecture then
it shows clearly how generic that file is and no one should have any
objection as long as nothing breaks and because of generic percentage
(percentage above 70 % will be better one). And collect acks from
maintainers and send pull request to Linus.

If you also provide complete diff, then it looks much better.

And if you need my help just ping me :-)

Thanks,
--
JSR

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