From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Geliang Tang <geliangtang@163.com>
Cc: Alessandro Zummo <a.zummo@towertech.it>,
rtc-linux@googlegroups.com, linux-kernel@vger.kernel.org
Subject: [rtc-linux] Re: [PATCH 1/2] rtc: fix module reference count in rtc-proc
Date: Mon, 30 Nov 2015 20:03:50 +0100 [thread overview]
Message-ID: <20151130190350.GI22136@piout.net> (raw)
In-Reply-To: <9d57abe4fe1acdbc4a63496142ea4b78f152e621.1446868545.git.geliangtang@163.com>
On 07/11/2015 at 12:00:21 +0800, Geliang Tang wrote :
> rtc-proc.c is not built as a module. Thus, rather than dealing with
> THIS_MODULE's reference count, we should deal with rtc->owner's
> reference count.
>
> Signed-off-by: Geliang Tang <geliangtang@163.com>
> ---
> drivers/rtc/rtc-proc.c | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
Both patches are applied, thanks.
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
--
--
You received this message because you are subscribed to "rtc-linux".
Membership options at http://groups.google.com/group/rtc-linux .
Please read http://groups.google.com/group/rtc-linux/web/checklist
before submitting a driver.
---
You received this message because you are subscribed to the Google Groups "rtc-linux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rtc-linux+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
prev parent reply other threads:[~2015-11-30 19:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-07 4:00 [rtc-linux] [PATCH 1/2] rtc: fix module reference count in rtc-proc Geliang Tang
2015-11-07 4:00 ` [rtc-linux] [PATCH 2/2] rtc: efi: add efi_procfs in efi_rtc_ops Geliang Tang
2015-11-25 0:05 ` [rtc-linux] " Alexandre Belloni
2015-11-30 19:03 ` Alexandre Belloni [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=20151130190350.GI22136@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=a.zummo@towertech.it \
--cc=geliangtang@163.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rtc-linux@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox