Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1490584
| From | arvind Yadav <arvind.yadav.cs@gmail.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH V3] clocksource/timer-imx-gpt: Preventing resource leakage in error case. |
| Date | 2016-09-24 09:50 +0200 |
| Message-ID | <skPSF-6AA-5@gated-at.bofh.it> (permalink) |
| References | <skxj4-38t-27@gated-at.bofh.it> <skBPI-6j6-37@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Thanks for help and suggestion.
I am looking 'Documentation/SubmittingPatches'.
Thanks
-Arvind Yadav
On Friday 23 September 2016 10:11 PM, Thomas Gleixner wrote:
> On Fri, 23 Sep 2016, Arvind Yadav wrote:
>
> So last time (V2) you had a almost perfect subject line:
>
> clocksrouce/timer-imz-gpt: Prevent resource leaks in error path
>
> The only issue was the clocksrcouce typo. Now you made it:
>
> clocksource/timer-imx-gpt: Preventing resource leakage in error case.
>
> Documentation/SubmittingPatches says:
>
> Describe your changes in imperative mood ... as if you are giving orders
> to the codebase to change its behaviour.
>
> "Preventing" is not imperative and the above is not a proper sentence,
> while the V2 one is.
>
>> ret = _mxc_timer_init(imxtm);
>> - if (ret)
>> - return ret;
>> + if (ret) {
>> + goto error_iounmap;
>> + }
> Further Documentation/SubmittingPatches also tells you which tools to use
> _before_ submission. If you'd used them then the above change would look
> different. You surely can figure that out yourself.
>
> Thanks,
>
> tglx
>
>
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: [PATCH V3] clocksource/timer-imx-gpt: Preventing resource leakage in error case. Thomas Gleixner <tglx@linutronix.de> - 2016-09-23 18:50 +0200 Re: [PATCH V3] clocksource/timer-imx-gpt: Preventing resource leakage in error case. arvind Yadav <arvind.yadav.cs@gmail.com> - 2016-09-24 09:50 +0200
csiph-web