From: Jingoo Han <jg1.han@samsung.com>
To: Venu Byravarasu <vbyravarasu@nvidia.com>
Cc: "'Andrew Morton'" <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"'Tejun Heo'" <tj@kernel.org>, "'Greg KH'" <greg@kroah.com>,
"'Alessandro Zummo'" <a.zummo@towertech.it>,
"rtc-linux@googlegroups.com" <rtc-linux@googlegroups.com>,
Jingoo Han <jg1.han@samsung.com>
Subject: Re: [PATCH v3] rtc: add devm_rtc_device_{register,unregister}()
Date: Wed, 06 Mar 2013 06:12:44 +0000 (GMT) [thread overview]
Message-ID: <12429277.417351362550362880.JavaMail.weblogic@epml07> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=euc-kr, Size: 1558 bytes --]
On Wednesday, March 06, 2013 3:03 PM, Venu Byravarasu wrote:
>
> > --- a/drivers/rtc/class.c
> > +++ b/drivers/rtc/class.c
>
> > +/**
> > + * devm_rtc_device_register - resource managed rtc_device_register()
> > + * @name: the name of the device
> > + * @dev: the device to register
> > + * @ops: the rtc operations structure
> > + * @owner: the module owner
> > + *
> > + * @return a struct rtc on success, or an ERR_PTR on error
> > + *
> > + * Managed rtc_device_register(). The rtc_device returned from this
> > function
> > + * are automatically freed on driver detach. See rtc_device_register()
> > + * for more information.
> > + */
> > +
> > +struct rtc_device *devm_rtc_device_register(const char *name,
> > + struct device *dev,
>
> As most of devm_* functions use " struct device *dev" as their first param,
> why not this function also modified to be in sync with them?
Yes, but, I want to sync with the form of rtc_device_register().
This function already uses 'struct device *dev' as second argument as below.
struct rtc_device *rtc_device_register(const char *name, struct device *dev,
const struct rtc_class_ops *ops,
struct module *owner)
Best regards,
Jingoo Han
>
> > + const struct rtc_class_ops *ops,
> > + struct module *owner)
> > +{
> > + struct rtc_device **ptr, *rtc;
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next reply other threads:[~2013-03-06 6:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-06 6:12 Jingoo Han [this message]
2013-03-06 6:18 ` [PATCH v3] rtc: add devm_rtc_device_{register,unregister}() Venu Byravarasu
2013-03-06 6:36 ` Jingoo Han
-- strict thread matches above, loose matches on Subject: below --
2013-03-06 6:37 Jingoo Han
2013-02-26 1:49 Jingoo Han
2013-02-26 1:50 ` 'Tejun Heo'
2013-03-06 6:03 ` Venu Byravarasu
2013-03-06 17:42 ` Stephen Boyd
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=12429277.417351362550362880.JavaMail.weblogic@epml07 \
--to=jg1.han@samsung.com \
--cc=a.zummo@towertech.it \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rtc-linux@googlegroups.com \
--cc=tj@kernel.org \
--cc=vbyravarasu@nvidia.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.