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: <55264414.3060902@unitn.it>
Date:	Thu, 09 Apr 2015 11:19:16 +0200
From:	Luca Abeni <luca.abeni@...tn.it>
To:	Peter Zijlstra <peterz@...radead.org>
CC:	Luca Abeni <lucabe72@...il.com>, henrik@...tad.us,
	juri.lelli@...il.com, raistlin@...ux.it, mingo@...nel.org,
	linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org
Subject: Re: [RFC 0/4] SCHED_DEADLINE documentation update

On 04/09/2015 11:17 AM, Peter Zijlstra wrote:
> On Thu, Apr 09, 2015 at 11:13:10AM +0200, Luca Abeni wrote:
>> Ok; so how should I proceed? Should I address the various comments (by you, Juri
>> and Henrik) by sending incremental patches based on these ones (since I see you queued
>> these patches), or should I resend everything after addressing the various comments?
>
> Whichever you prefer, if you'd like to just respin these patches that's
> fine, I'll drop them -- but let me know before they end up in a git tree
> ;-)
Ok; given Henrik's comments, I suspect it is better to respin the patches.
I hope to resend everything in few days.


			Thanks,
				Luca

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ