Re: [PATCH 5/5] cris: nand: Split a condition check in crisv32_nand_flash_probe()

2017-10-04 Thread Alexander Sverdlin
Hello Markus, On 04/10/17 20:50, SF Markus Elfring wrote: > * Split a condition check for failed calls of the function "ioremap" > so that the return value in the variable "write_cs" will also be > immediately checked. > > * Adjust jump targets according to the Linux coding style convention.

Re: [PATCH 5/5] cris: nand: Split a condition check in crisv32_nand_flash_probe()

2017-10-04 Thread Alexander Sverdlin
Hello Markus, On 04/10/17 20:50, SF Markus Elfring wrote: > * Split a condition check for failed calls of the function "ioremap" > so that the return value in the variable "write_cs" will also be > immediately checked. > > * Adjust jump targets according to the Linux coding style convention.

[PATCH 5/5] cris: nand: Split a condition check in crisv32_nand_flash_probe()

2017-10-04 Thread SF Markus Elfring
From: Markus Elfring Date: Wed, 4 Oct 2017 20:02:12 +0200 * Split a condition check for failed calls of the function "ioremap" so that the return value in the variable "write_cs" will also be immediately checked. * Adjust jump targets according to the Linux

[PATCH 5/5] cris: nand: Split a condition check in crisv32_nand_flash_probe()

2017-10-04 Thread SF Markus Elfring
From: Markus Elfring Date: Wed, 4 Oct 2017 20:02:12 +0200 * Split a condition check for failed calls of the function "ioremap" so that the return value in the variable "write_cs" will also be immediately checked. * Adjust jump targets according to the Linux coding style convention.