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]
Date:	Sun, 01 May 2011 12:59:35 -0300
From:	Mauro Carvalho Chehab <mchehab@...hat.com>
To:	Florian Mickler <florian@...kler.org>
CC:	linux-kernel@...r.kernel.org, linux-media@...r.kernel.org,
	crope@....fi, tvboxspy@...il.com
Subject: Re: [PATCH 0/5] get rid of on-stack dma buffers (part1)

Em 01-05-2011 07:38, Florian Mickler escreveu:
> On Sat, 30 Apr 2011 19:30:52 -0300
> Mauro Carvalho Chehab <mchehab@...hat.com> wrote:
> 
>> Hi Florian,
>>
>> Em 30-04-2011 15:54, Florian Mickler escreveu:
>>> Hi Mauro!
>>>
>>> I just saw that you picked up some patches of mine. What about these?
>>> These are actually tested...
>>
>> I'm still in process of applying the pending patches. Due to patchwork.kernel.org
>> troubles (including the loss of about 270 patches from its SQL database only 
>> recovered yesterday[1]), I have a long backlog. So, I'm gradually applying the remaing
>> stuff. It will take some time though, and it will depend on patchwork mood, but I intend
>> to spend some time during this weekend to minimize the backlog.
>>
>>
>> Cheers,
>> Mauro
>>
>> [1] The recover lost the email's body/SOB, so I've wrote a script to use my email
>> queue to get the data, using patchwork just to mark what patches were already
>> processed. This increses the time I have to spend on each patch, as I need to run
>> a script to match the patchwork patch with the patch ID inside my email queue.
>>
> 
> Ah ok, no time pressure over here.. just wanted to make sure
> that these don't get lost.

I think I've applied your series yesterday. Yet, patchwork is currently at bad mood, and it is
not allowing to mark your patches as applied (and the previous series as superseded).

I suspect that I'll need to completely abandon patchwork and work on a new way for handling it
that doesn't depend (nor will update) patchwork.kernel.org.

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