From: Jungseung Lee <js07.lee@samsung.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Richard Cochran <richardcochran@gmail.com>,
linux-kernel@vger.kernel.org
Cc: Jungseung Lee <js07.lee@samsung.com>
Subject: [PATCH] posix-clock: remove unneeded posix_clock_compat_ioctl()
Date: Wed, 01 Jun 2016 17:54:41 +0900 [thread overview]
Message-ID: <1464771281-13248-1-git-send-email-js07.lee@samsung.com> (raw)
posix_clock_compat_ioctl() is identical to posix_clock_ioctl().
We don't need additional compat_ioctl in this time.
Remove posix_clock_compat_ioctl() and let posix_clock_ioctl() is in charge.
Signed-off-by: Jungseung Lee <js07.lee@samsung.com>
---
kernel/time/posix-clock.c | 22 ----------------------
1 file changed, 22 deletions(-)
diff --git a/kernel/time/posix-clock.c b/kernel/time/posix-clock.c
index 9cff0ab..d46ac80 100644
--- a/kernel/time/posix-clock.c
+++ b/kernel/time/posix-clock.c
@@ -131,25 +131,6 @@ static long posix_clock_ioctl(struct file *fp,
return err;
}
-#ifdef CONFIG_COMPAT
-static long posix_clock_compat_ioctl(struct file *fp,
- unsigned int cmd, unsigned long arg)
-{
- struct posix_clock *clk = get_posix_clock(fp);
- int err = -ENOTTY;
-
- if (!clk)
- return -ENODEV;
-
- if (clk->ops.ioctl)
- err = clk->ops.ioctl(clk, cmd, arg);
-
- put_posix_clock(clk);
-
- return err;
-}
-#endif
-
static int posix_clock_open(struct inode *inode, struct file *fp)
{
int err;
@@ -201,9 +182,6 @@ static const struct file_operations posix_clock_file_operations = {
.release = posix_clock_release,
.fasync = posix_clock_fasync,
.mmap = posix_clock_mmap,
-#ifdef CONFIG_COMPAT
- .compat_ioctl = posix_clock_compat_ioctl,
-#endif
};
int posix_clock_register(struct posix_clock *clk, dev_t devid)
--
1.7.9.5
next reply other threads:[~2016-06-01 8:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-01 8:54 Jungseung Lee [this message]
2016-06-01 14:32 ` [PATCH] posix-clock: remove unneeded posix_clock_compat_ioctl() Richard Cochran
2016-06-06 13:59 ` Thomas Gleixner
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=1464771281-13248-1-git-send-email-js07.lee@samsung.com \
--to=js07.lee@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=tglx@linutronix.de \
/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