From: Jingoo Han <jg1.han@samsung.com>
To: "'Tejun Heo'" <tj@kernel.org>
Cc: "'Andrew Morton'" <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, "'Greg KH'" <greg@kroah.com>,
"'Alessandro Zummo'" <a.zummo@towertech.it>,
rtc-linux@googlegroups.com, "'Jingoo Han'" <jg1.han@samsung.com>
Subject: Re: [PATCH V2] rtc: add devm_rtc_device_{register,unregister}()
Date: Tue, 26 Feb 2013 10:42:07 +0900 [thread overview]
Message-ID: <008f01ce13c2$7c9e37d0$75daa770$%han@samsung.com> (raw)
In-Reply-To: <20130226013000.GG2679@htj.dyndns.org>
On Tuesday, February 26, 2013 10:30 AM, Tejun Heo wrote:
>
> On Mon, Feb 25, 2013 at 05:23:17PM -0800, 'Tejun Heo' wrote:
> > again, why do we need the WARN_ON() at all given that other
> > devm_*_match() don't do that and the only way to get NULL there would
> > be bug in devm_rtc*() code itself rather than its users?
>
> Ughh... I see that you probably copied the chunk from clk / regulator
> implementation. Let's please not copy those. Input validation via
> WARN_ON()s is nice when the interface is taking input from outside or
> the code in question is complex / fragile. Here, the code involved is
> like 20 lines and self-contained.
OK, I see.
Thank you for your comment.
I will send v3 patch soon :)
Best regards,
Jingoo Han
>
> Thanks.
>
> --
> tejun
next prev parent reply other threads:[~2013-02-26 1:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 1:21 [PATCH V2] rtc: add devm_rtc_device_{register,unregister}() Jingoo Han
2013-02-26 1:23 ` 'Tejun Heo'
2013-02-26 1:30 ` 'Tejun Heo'
2013-02-26 1:42 ` Jingoo Han [this message]
2013-02-26 22:33 ` Dmitry Torokhov
2013-02-27 2:12 ` Jingoo Han
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='008f01ce13c2$7c9e37d0$75daa770$%han@samsung.com' \
--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 \
/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