From: chenlibo.3@gmail.com (Libo Chen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] usb: gadget: s3c2410: fix clk resource leak and update
Date: Sat, 11 May 2013 19:27:48 +0800 [thread overview]
Message-ID: <518E2B34.7080503@gmail.com> (raw)
In-Reply-To: <1684189.YrZqmJjoym@flatron>
? 2013-5-11 18:15, Tomasz Figa ??:
> Hi Libo,
>
> On Saturday 11 of May 2013 14:28:15 Libo Chen wrote:
>> >From: Libo Chen<libo.chen@huawei.com>
> The patch subject is slightly misleading. It suggests that the patch only
> changes clock handling, but in fact the biggest part of the patch is
> conversion to devm_ helpers.
>
> I think following subject would suit this patch better:
>
> [PATCH] usb: gadget: s3c2410: Convert to managed resource allocation
>
> What do you think?
>
> Also please see my comments inline.
>
Hi Tomasz,
Thank you for your remind. Sorry, I forgeted to add RFC.
"Convert to managed resource allocation" is more suitable.
Your advice is very helpfull for me to understand those interfaces.
I will be careful in the future patches.
Thanks again
prev parent reply other threads:[~2013-05-11 11:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-11 6:28 [PATCH] usb: gadget: s3c2410: fix clk resource leak and update Libo Chen
2013-05-11 10:15 ` Tomasz Figa
2013-05-11 11:27 ` Libo Chen [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=518E2B34.7080503@gmail.com \
--to=chenlibo.3@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).