CONTATE URGENTEMENTE O DIRETOR DO BANCO ORA..docx
Description: MS-Word 2007 document
On 06/18/17 07:05, Rob Herring wrote:
> On Tue, Jun 13, 2017 at 07:49:04PM -0700, frowand.l...@gmail.com wrote:
>> From: Frank Rowand
>>
>> The Devicetree Specification has superseded the ePAPR as the
>> base specification for bindings. Update files in Documentat
Hi,
> -Original Message-
> From: Simon Baatz [mailto:gmbno...@gmail.com]
> Sent: Sunday, May 06, 2012 00:50
> To: Frank; 'Sebastian Andrzej Siewior'; u...@jdland.co.il; linux-
> cry...@vger.kernel.org; Herbert Xu; Catalin Marinas; linux-arm-
> ker...@list
] EIP: [] shash_async_export+0x9/0xd SS:ESP 0069:dccebe44
[ 301.693116] CR2: ffe8
[ 301.693116] ---[ end trace a7919e7f17c0a727 ]---
Regards,
Frank
--
To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
the body of a message to majord...@vger.kernel.org
More
d 7c cc cc b5 cf 1b d6 c7 ab d0 25 c4 21
[490889.476068] 0010: 66 0b 8e 70
Using SHA1 in a ssl/tls handshake fails in tests with mv_cesa loaded, which
might be related to this.
Regards,
Frank
--
To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
the body of
Geert Uytterhoeven wrote:
> It's shorter.
>
> Especially `pr_err' fits in the space of `printk', so you don't have to split
> lines that become to long due to adding the KERN_*.
Ah, i see. Thanks for the explanation :-)
Frank
--
To unsubscribe from this list:
Geert Uytterhoeven wrote:
> BTW, why are you using printk(KERN_INFO "..."), and not pr_info("...")?
Without special reason. Is pr_info preferred?
Thanks,
Frank
--
To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
the body of a message
Geert Uytterhoeven wrote:
> On Wed, 25 Feb 2009, Frank Seidel wrote:
> Wel...
>
> Using kmalloc() increases code size, makes the code more complex, and
> increases
> the risk of introducing a memory leak now or later.
Ok, admitted.
>> I just stumbled over tcrypt on th
From: Frank Seidel
Applying kernel janitors todos (printk calls need KERN_*
constants on linebeginnings, reduce stack footprint where
possible) to tcrypts test_hash_speed (where stacks
memory footprint was very high (on i386 1184 bytes to
160 now).
Signed-off-by: Frank Seidel
---
crypto
er tcrypt on the make checkstack output and as also
the kerneljanitors todo advises to reduce this footprint where possible
i just wanted to help out here.
Thanks,
Frank
--
To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
the body of a message to majord...@vger.kernel.o
Thiago Galesi wrote:
> If you write static char output[1024]; (even inside a function) it's
> not allocated on the stack.
Oh, yes i misunderstood Herbert, sorry. But anyway isn't
it preferred to kmalloc such arrays?
Greg, i thought it was you who told me so, is that right?
Than
From: Frank Seidel
Applying kernel janitors todos (printk calls need KERN_*
constants on linebeginnings, reduce stack footprint where
possible) to tcrypts test_hash_speed (where stacks
memory footprint was very high (on i386 1184 bytes to
164 now).
Signed-off-by: Frank Seidel
---
crypto
Herbert Xu wrote:
>> -char output[1024];
>
> How about just making it static?
Well, it was static before. But there
are efforts to reduce current stack memory
footprints.
Frank
--
To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
the body
From: Frank Seidel
Applying kernel janitors todos (printk calls need KERN_*
constants on linebeginnings, reduce stack footprint where
possible) to tcrypts test_hash_speed (where stacks
memory footprint was very high (on i386 1184 bytes to
292 now).
Signed-off-by: Frank Seidel
---
crypto
From: Frank Seidel
According to kerneljanitors todo list all printk calls (beginning
a new line) should have an according KERN_* constant.
Those are the missing pieces here for the crypto subsystem.
Signed-off-by: Frank Seidel
---
crypto/ansi_cprng.c |2 +-
crypto/tcrypt.c | 51
Herbert Xu wrote:
> Please do. If it doesn't have any markings at least we know that
> it needs fixing. If you just add WARNINGs then we lose that
> information.
Thats right, i fully agree. So i'll redo it asap.
Thanks,
Frank
--
To unsubscribe from this list: send the line
Alexey Dobriyan schrieb:
> On Fri, Feb 06, 2009 at 03:19:10PM +0100, Frank Seidel wrote:
>> According to kerneljanitors todo list all printk calls (beginning
>> a new line) should have an according KERN_* constant.
>
> Forget about kernel janitors todo list, fix a bug inste
hink its worth/i should redo it and adapt the loglevel
more appropriate?
Thanks,
Frank
--
To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
From: Frank Seidel
According to kerneljanitors todo list all printk calls (beginning
a new line) should have an according KERN_* constant.
Those are the missing pieces here for the crypto subsystem.
Signed-off-by: Frank Seidel
---
crypto/ansi_cprng.c |2 +-
crypto/tcrypt.c | 48
19 matches
Mail list logo
