From: Misono Tomohiro <misono.tomohiro@jp.fujitsu.com>
To: <linux-rtc@vger.kernel.org>
Cc: <a.zummo@towertech.it>, <alexandre.belloni@bootlin.com>,
<misono.tomohiro@jp.fujitsu.com>
Subject: [PATCH] rtc: cleanup obsolete comment about struct rtc_class_ops
Date: Fri, 10 Jul 2020 17:00:03 +0900 [thread overview]
Message-ID: <20200710080003.7986-1-misono.tomohiro@jp.fujitsu.com> (raw)
Commit ea369ea6d828 ("rtc: remove .open() and .release()") removes
open/release callback from struct rtc_class_ops.
Also commit 80d4bb515b78 ("RTC: Cleanup rtc_class_ops->irq_set_state")
and commit 696160fec162 ("RTC: Cleanup rtc_class_ops->irq_set_freq()")
removes irq callbacks.
So, just remove related comments so that readers will not be confused.
Signed-off-by: Misono Tomohiro <misono.tomohiro@jp.fujitsu.com>
---
include/linux/rtc.h | 4 ----
1 file changed, 4 deletions(-)
diff --git a/include/linux/rtc.h b/include/linux/rtc.h
index bba3db3f7efa..22d1575e4991 100644
--- a/include/linux/rtc.h
+++ b/include/linux/rtc.h
@@ -55,10 +55,6 @@ extern struct class *rtc_class;
*
* The (current) exceptions are mostly filesystem hooks:
* - the proc() hook for procfs
- * - non-ioctl() chardev hooks: open(), release()
- *
- * REVISIT those periodic irq calls *do* have ops_lock when they're
- * issued through ioctl() ...
*/
struct rtc_class_ops {
int (*ioctl)(struct device *, unsigned int, unsigned long);
--
2.21.3
next reply other threads:[~2020-07-10 8:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 8:00 Misono Tomohiro [this message]
2020-07-16 11:35 ` [PATCH] rtc: cleanup obsolete comment about struct rtc_class_ops Alexandre Belloni
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=20200710080003.7986-1-misono.tomohiro@jp.fujitsu.com \
--to=misono.tomohiro@jp.fujitsu.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=linux-rtc@vger.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;
as well as URLs for NNTP newsgroup(s).