Re: [PATCH v2 06/19] PM / devfreq: tegra: Fix missed error checking on devfreq initialization failure

2019-04-16 Thread Chanwoo Choi
Hi, On 19. 4. 16. 오후 11:29, Dmitry Osipenko wrote: > 16.04.2019 5:32, Chanwoo Choi пишет: >> Hi, >> >> patch6/7/8/9 are for handling of exception handling in probe() function. >> Actually, I'm not sure that there are special reason to split out >> the patches. I think that you can squash

Re: [PATCH v2 06/19] PM / devfreq: tegra: Fix missed error checking on devfreq initialization failure

2019-04-16 Thread Dmitry Osipenko
16.04.2019 5:32, Chanwoo Choi пишет: > Hi, > > patch6/7/8/9 are for handling of exception handling in probe() function. > Actually, I'm not sure that there are special reason to split out > the patches. I think that you can squash patch6/7/8/9 to only one patch. Indeed, I was rebasing and

Re: [PATCH v2 06/19] PM / devfreq: tegra: Fix missed error checking on devfreq initialization failure

2019-04-15 Thread Chanwoo Choi
Hi, patch6/7/8/9 are for handling of exception handling in probe() function. Actually, I'm not sure that there are special reason to split out the patches. I think that you can squash patch6/7/8/9 to only one patch. Also, even if patch6/7/8/9 handle the exception handling in probe(), the

[PATCH v2 06/19] PM / devfreq: tegra: Fix missed error checking on devfreq initialization failure

2019-04-15 Thread Dmitry Osipenko
The code doesn't check for devfreq initialization failure, fix it. Signed-off-by: Dmitry Osipenko --- drivers/devfreq/tegra-devfreq.c | 4 1 file changed, 4 insertions(+) diff --git a/drivers/devfreq/tegra-devfreq.c b/drivers/devfreq/tegra-devfreq.c index f0f0d78f6cbf..aa0478464b35 100644