On Mon, Mar 27, 2017 at 2:24 AM, SF Markus Elfring
wrote:
>> However, I agree with Casey that this patch is mostly just code churn
>> so I'm going to drop this from your series.
>
> How do you think about to return only constant error codes in this function?
> Would it be acceptable to replace any
> However, I agree with Casey that this patch is mostly just code churn
> so I'm going to drop this from your series.
How do you think about to return only constant error codes in this function?
Would it be acceptable to replace any statements “goto out;” with
“return -ENOMEM;” here instead?
Rega
On Sun, Jan 15, 2017 at 10:04 AM, SF Markus Elfring
wrote:
> From: Markus Elfring
> Date: Sat, 14 Jan 2017 13:40:25 +0100
>
> The local variable "rc" was reset with an error code up to five times
> before a memory allocation failure was detected.
>
> Add a jump target so that this assignment will
On 1/15/2017 7:04 AM, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Sat, 14 Jan 2017 13:40:25 +0100
>
> The local variable "rc" was reset with an error code up to five times
> before a memory allocation failure was detected.
>
> Add a jump target so that this assignment will only be perf
From: Markus Elfring
Date: Sat, 14 Jan 2017 13:40:25 +0100
The local variable "rc" was reset with an error code up to five times
before a memory allocation failure was detected.
Add a jump target so that this assignment will only be performed after
a concrete software failure.
Signed-off-by: Ma
5 matches
Mail list logo
