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] [day] [month] [year] [list]
Date:	Mon, 19 Mar 2012 16:49:54 -0400
From:	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
To:	dledford@...hat.com
CC:	kosaki.motohiro@...fujitsu.com, akpm@...ux-foundation.org,
	kosaki.motohiro@...il.com, linux-kernel@...r.kernel.org,
	amwang@...hat.com, jslaby@...e.cz, ebiederm@...ssion.com,
	joe.korty@...r.com, dhowells@...hat.com
Subject: Re: [resend][PATCH 1/3] mqueue: revert bump up DFLT_*MAX

On 3/19/2012 2:16 PM, Doug Ledford wrote:
> ----- Original Message -----
>> On 3/14/2012 5:45 PM, Doug Ledford wrote:
>>> On 03/14/2012 05:38 PM, Andrew Morton wrote:
>>>> On Wed, 14 Mar 2012 17:28:33 -0400
>>>> Doug Ledford <dledford@...hat.com> wrote:
>>>>
>>>>> This has obviously fallen through the cracks.
>>>>
>>>> It sure has.  Please dig out whatever is the currently favored
>>>> patchset, refresh, retest and resend, with changelogging which
>>>> fully
>>>> covers the reasoning and decision process?
>>>
>>> OK, completely redoing patch set then against current Linus tree.
>>>
>>> Motohiro, would you be so kind as to resend my your patches that
>>> went on
>>> top of mine and I'll create a complete patch set?
>>
>> I'm sorry. I already have a rebased patch. but I haven't posted. I
>> have toa
>> hurry.
> 
> Actually, I already pulled them from the lkml archives and fixed up
> the one patch that didn't apply cleanly.  The only reason I haven't
> sent the entire patchset out yet is that I'm writing a test/verification
> app to go along with it.

OK, I'll stop this work then. Good luck. :)

But, please rebase the patch on top linux-next. It's more akpm happy and
you are going to see more conflicts. That's the reason why I thought I
need more tests.

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