From: arvind Yadav <arvind.yadav.cs@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: baohua@kernel.org, daniel.lezcano@linaro.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V3] clocksource/timer-imx-gpt: Preventing resource leakage in error case.
Date: Sat, 24 Sep 2016 13:10:19 +0530 [thread overview]
Message-ID: <dc7aa0af-8788-2159-8f87-5810e88aead1@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1609231831170.5640@nanos>
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
>
>
prev parent reply other threads:[~2016-09-24 7:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 11:57 Arvind Yadav
2016-09-23 16:41 ` Thomas Gleixner
2016-09-24 7:40 ` arvind Yadav [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dc7aa0af-8788-2159-8f87-5810e88aead1@gmail.com \
--to=arvind.yadav.cs@gmail.com \
--cc=baohua@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome