On Sat, Jan 27, 2018 at 09:15:09PM +0100, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Sat, 27 Jan 2018 21:10:12 +0100
>
> Two update suggestions were taken into account
> from static source code analysis.
>
> Markus Elfring (2):
> Delete two error
On Sat, Jan 27, 2018 at 09:15:09PM +0100, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Sat, 27 Jan 2018 21:10:12 +0100
>
> Two update suggestions were taken into account
> from static source code analysis.
>
> Markus Elfring (2):
> Delete two error messages for a failed memory
On 01/27/2018 03:15 PM, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Sat, 27 Jan 2018 21:10:12 +0100
>
> Two update suggestions were taken into account
> from static source code analysis.
>
> Markus Elfring (2):
> Delete two error messages for a
On 01/27/2018 03:15 PM, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Sat, 27 Jan 2018 21:10:12 +0100
>
> Two update suggestions were taken into account
> from static source code analysis.
>
> Markus Elfring (2):
> Delete two error messages for a failed memory allocation
> Use
On Mon, Jan 29, 2018 at 3:01 PM, SF Markus Elfring
wrote:
>> You don't need 2 patches when changing same lines of code.
>
> Are these really the same?
>
>
>> Could you squash both and send your changes in a single patch.
>
> I prefer to keep the deletion of
On Mon, Jan 29, 2018 at 3:01 PM, SF Markus Elfring
wrote:
>> You don't need 2 patches when changing same lines of code.
>
> Are these really the same?
>
>
>> Could you squash both and send your changes in a single patch.
>
> I prefer to keep the deletion of questionable error messages separate
>
> You don't need 2 patches when changing same lines of code.
Are these really the same?
> Could you squash both and send your changes in a single patch.
I prefer to keep the deletion of questionable error messages separate
from the refactoring for a bit of exception handling.
> The patches
> You don't need 2 patches when changing same lines of code.
Are these really the same?
> Could you squash both and send your changes in a single patch.
I prefer to keep the deletion of questionable error messages separate
from the refactoring for a bit of exception handling.
> The patches
On Sun, Jan 28, 2018 at 1:45 AM, SF Markus Elfring
wrote:
> From: Markus Elfring
> Date: Sat, 27 Jan 2018 21:10:12 +0100
>
> Two update suggestions were taken into account
> from static source code analysis.
You don't need 2 patches
On Sun, Jan 28, 2018 at 1:45 AM, SF Markus Elfring
wrote:
> From: Markus Elfring
> Date: Sat, 27 Jan 2018 21:10:12 +0100
>
> Two update suggestions were taken into account
> from static source code analysis.
You don't need 2 patches when changing same lines of code. Could
you squash both and
From: Markus Elfring
Date: Sat, 27 Jan 2018 21:10:12 +0100
Two update suggestions were taken into account
from static source code analysis.
Markus Elfring (2):
Delete two error messages for a failed memory allocation
Use common error handling code
From: Markus Elfring
Date: Sat, 27 Jan 2018 21:10:12 +0100
Two update suggestions were taken into account
from static source code analysis.
Markus Elfring (2):
Delete two error messages for a failed memory allocation
Use common error handling code
drivers/infiniband/hw/bnxt_re/qplib_res.c
12 matches
Mail list logo