Re: [PATCH 1/3] regulator: max8973: get rid of extra variable for gpio validity

2015-05-06 Thread Mark Brown
On Wed, May 06, 2015 at 05:39:28PM +0530, Laxman Dewangan wrote: > This patch is not available on linux-next. Is it pending for any clean-up? Ah, sorry - forgot to follow up on this. The patch doesn't apply against curent code, please check and resend. signature.asc Description: Digital

Re: [PATCH 1/3] regulator: max8973: get rid of extra variable for gpio validity

2015-05-06 Thread Laxman Dewangan
On Tuesday 21 April 2015 02:49 AM, Mark Brown wrote: * PGP Signed by an unknown key On Mon, Apr 20, 2015 at 06:24:15PM +0530, Laxman Dewangan wrote: To find that dvs-gpio is valid or not, gpio API gpio_is_valid() can be directly used instead of intermediate variable. Applied, thanks. This

Re: [PATCH 1/3] regulator: max8973: get rid of extra variable for gpio validity

2015-05-06 Thread Mark Brown
On Wed, May 06, 2015 at 05:39:28PM +0530, Laxman Dewangan wrote: This patch is not available on linux-next. Is it pending for any clean-up? Ah, sorry - forgot to follow up on this. The patch doesn't apply against curent code, please check and resend. signature.asc Description: Digital

Re: [PATCH 1/3] regulator: max8973: get rid of extra variable for gpio validity

2015-05-06 Thread Laxman Dewangan
On Tuesday 21 April 2015 02:49 AM, Mark Brown wrote: * PGP Signed by an unknown key On Mon, Apr 20, 2015 at 06:24:15PM +0530, Laxman Dewangan wrote: To find that dvs-gpio is valid or not, gpio API gpio_is_valid() can be directly used instead of intermediate variable. Applied, thanks. This

Re: [PATCH 1/3] regulator: max8973: get rid of extra variable for gpio validity

2015-04-20 Thread Mark Brown
On Mon, Apr 20, 2015 at 06:24:15PM +0530, Laxman Dewangan wrote: > To find that dvs-gpio is valid or not, gpio API gpio_is_valid() > can be directly used instead of intermediate variable. Applied, thanks. signature.asc Description: Digital signature

Re: [PATCH 1/3] regulator: max8973: get rid of extra variable for gpio validity

2015-04-20 Thread Mark Brown
On Mon, Apr 20, 2015 at 06:24:15PM +0530, Laxman Dewangan wrote: > To find that dvs-gpio is valid or not, gpio API gpio_is_valid() > can be directly used instead of intermediate variable. > Removing the extra variable and using the gpio_is_valid(). This still looks like it's got the same issue

[PATCH 1/3] regulator: max8973: get rid of extra variable for gpio validity

2015-04-20 Thread Laxman Dewangan
To find that dvs-gpio is valid or not, gpio API gpio_is_valid() can be directly used instead of intermediate variable. Removing the extra variable and using the gpio_is_valid(). Signed-off-by: Laxman Dewangan --- This is same as earlier patch. Making this as part of this series.

Re: [PATCH 1/3] regulator: max8973: get rid of extra variable for gpio validity

2015-04-20 Thread Mark Brown
On Mon, Apr 20, 2015 at 06:24:15PM +0530, Laxman Dewangan wrote: To find that dvs-gpio is valid or not, gpio API gpio_is_valid() can be directly used instead of intermediate variable. Applied, thanks. signature.asc Description: Digital signature

[PATCH 1/3] regulator: max8973: get rid of extra variable for gpio validity

2015-04-20 Thread Laxman Dewangan
To find that dvs-gpio is valid or not, gpio API gpio_is_valid() can be directly used instead of intermediate variable. Removing the extra variable and using the gpio_is_valid(). Signed-off-by: Laxman Dewangan ldewan...@nvidia.com --- This is same as earlier patch. Making this as part of this

Re: [PATCH 1/3] regulator: max8973: get rid of extra variable for gpio validity

2015-04-20 Thread Mark Brown
On Mon, Apr 20, 2015 at 06:24:15PM +0530, Laxman Dewangan wrote: To find that dvs-gpio is valid or not, gpio API gpio_is_valid() can be directly used instead of intermediate variable. Removing the extra variable and using the gpio_is_valid(). This still looks like it's got the same issue with