Re: [PATCH 0/6] regulator: max77686/802: Cleanup

2014-11-05 Thread Krzysztof Kozlowski
On wto, 2014-11-04 at 20:42 +, Mark Brown wrote: > On Tue, Nov 04, 2014 at 10:25:22AM +0100, Krzysztof Kozlowski wrote: > > > Probably I should rebase it on newer next or regulator tree because > > yesterdays Javier's changes were applied. The merge conflict is trivial > > to solve (only

Re: [PATCH 0/6] regulator: max77686/802: Cleanup

2014-11-05 Thread Krzysztof Kozlowski
On wto, 2014-11-04 at 20:42 +, Mark Brown wrote: On Tue, Nov 04, 2014 at 10:25:22AM +0100, Krzysztof Kozlowski wrote: Probably I should rebase it on newer next or regulator tree because yesterdays Javier's changes were applied. The merge conflict is trivial to solve (only removal of

Re: [PATCH 0/6] regulator: max77686/802: Cleanup

2014-11-04 Thread Mark Brown
On Tue, Nov 04, 2014 at 10:25:22AM +0100, Krzysztof Kozlowski wrote: > Probably I should rebase it on newer next or regulator tree because > yesterdays Javier's changes were applied. The merge conflict is trivial > to solve (only removal of lines). > Mark, let me know if you want me to resubmit

Re: [PATCH 0/6] regulator: max77686/802: Cleanup

2014-11-04 Thread Krzysztof Kozlowski
On wto, 2014-11-04 at 09:49 +0100, Krzysztof Kozlowski wrote: > Hi, > > > Previously this patchset was part of adding GPIO to max77686 > regulator driver [1]. I split it but the goal is the same: > cleanup and simplify the regulator drivers by removing obsolete > board file support so adding new

Re: [PATCH 0/6] regulator: max77686/802: Cleanup

2014-11-04 Thread Javier Martinez Canillas
Hello Krzysztof, On 11/04/2014 09:49 AM, Krzysztof Kozlowski wrote: > Previously this patchset was part of adding GPIO to max77686 > regulator driver [1]. I split it but the goal is the same: > cleanup and simplify the regulator drivers by removing obsolete > board file support so adding new

[PATCH 0/6] regulator: max77686/802: Cleanup

2014-11-04 Thread Krzysztof Kozlowski
Hi, Previously this patchset was part of adding GPIO to max77686 regulator driver [1]. I split it but the goal is the same: cleanup and simplify the regulator drivers by removing obsolete board file support so adding new features would be easier. The patchset removes board file support from

[PATCH 0/6] regulator: max77686/802: Cleanup

2014-11-04 Thread Krzysztof Kozlowski
Hi, Previously this patchset was part of adding GPIO to max77686 regulator driver [1]. I split it but the goal is the same: cleanup and simplify the regulator drivers by removing obsolete board file support so adding new features would be easier. The patchset removes board file support from

Re: [PATCH 0/6] regulator: max77686/802: Cleanup

2014-11-04 Thread Javier Martinez Canillas
Hello Krzysztof, On 11/04/2014 09:49 AM, Krzysztof Kozlowski wrote: Previously this patchset was part of adding GPIO to max77686 regulator driver [1]. I split it but the goal is the same: cleanup and simplify the regulator drivers by removing obsolete board file support so adding new features

Re: [PATCH 0/6] regulator: max77686/802: Cleanup

2014-11-04 Thread Krzysztof Kozlowski
On wto, 2014-11-04 at 09:49 +0100, Krzysztof Kozlowski wrote: Hi, Previously this patchset was part of adding GPIO to max77686 regulator driver [1]. I split it but the goal is the same: cleanup and simplify the regulator drivers by removing obsolete board file support so adding new

Re: [PATCH 0/6] regulator: max77686/802: Cleanup

2014-11-04 Thread Mark Brown
On Tue, Nov 04, 2014 at 10:25:22AM +0100, Krzysztof Kozlowski wrote: Probably I should rebase it on newer next or regulator tree because yesterdays Javier's changes were applied. The merge conflict is trivial to solve (only removal of lines). Mark, let me know if you want me to resubmit