> Well, as I said elsewhere, if you make the same type of change in
> multiple places in one piece of code (or code maintained by the same
> maintainer),
I can imagine that my update suggestions will also trigger some additional
development efforts. I assume that some contributors appreciate
fine
On Tue, Sep 6, 2016 at 5:38 AM, SF Markus Elfring
wrote:
>> Like in the other patch series I've just commented,
>
> Thanks for your quick response.
>
>
>> please put all label renames into one patch.
>
> Could you accept these update suggestions generally?
>
>
> I would prefer to avoid squashing s
> Like in the other patch series I've just commented,
Thanks for your quick response.
> please put all label renames into one patch.
Could you accept these update suggestions generally?
I would prefer to avoid squashing special changes together by default.
Regards,
Markus
On Mon, Sep 5, 2016 at 10:12 PM, SF Markus Elfring
wrote:
> From: Markus Elfring
> Date: Mon, 5 Sep 2016 22:05:05 +0200
>
> Some update suggestions were taken into account
> from static source code analysis.
>
> Markus Elfring (7):
> Fix a typo in a comment line
> Use kmalloc_array() in hest_
From: Markus Elfring
Date: Mon, 5 Sep 2016 22:05:05 +0200
Some update suggestions were taken into account
from static source code analysis.
Markus Elfring (7):
Fix a typo in a comment line
Use kmalloc_array() in hest_ghes_dev_register()
Move an assignment in hest_ghes_dev_register()
Rena
5 matches
Mail list logo
