From: Naveen Kumar Parna <parna.naveenku...@gmail.com>

There is no advantage to keep 'struct file_operations.open & .close'
API's. So removed the unnecessary code efi_rtc_open & efi_rtc_close.

Signed-off-by: Naveen Kumar Parna <parna.naveenku...@gmail.com>
---
 drivers/char/efirtc.c | 23 -----------------------
 1 file changed, 23 deletions(-)

diff --git a/drivers/char/efirtc.c b/drivers/char/efirtc.c
index d9aab643997e..11781ebffbf7 100644
--- a/drivers/char/efirtc.c
+++ b/drivers/char/efirtc.c
@@ -254,27 +254,6 @@ static long efi_rtc_ioctl(struct file *file, unsigned int 
cmd,
        return -ENOTTY;
 }
 
-/*
- *     We enforce only one user at a time here with the open/close.
- *     Also clear the previous interrupt data on an open, and clean
- *     up things on a close.
- */
-
-static int efi_rtc_open(struct inode *inode, struct file *file)
-{
-       /*
-        * nothing special to do here
-        * We do accept multiple open files at the same time as we
-        * synchronize on the per call operation.
-        */
-       return 0;
-}
-
-static int efi_rtc_close(struct inode *inode, struct file *file)
-{
-       return 0;
-}
-
 /*
  *     The various file operations we support.
  */
@@ -282,8 +261,6 @@ static int efi_rtc_close(struct inode *inode, struct file 
*file)
 static const struct file_operations efi_rtc_fops = {
        .owner          = THIS_MODULE,
        .unlocked_ioctl = efi_rtc_ioctl,
-       .open           = efi_rtc_open,
-       .release        = efi_rtc_close,
        .llseek         = no_llseek,
 };
 
-- 
2.17.1

Reply via email to