From: Jiri Olsa <olsajiri@gmail.com>
To: gregkh@suse.de
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: [PATCH] fs: removing unused fops from struct char_device_struct
Date: Wed, 20 Feb 2008 21:57:23 +0100 [thread overview]
Message-ID: <47BC9433.8020905@gmail.com> (raw)
Hi,
seems struct char_device_struct::fops is no longer used, removing it.
I checked with "make allyesconfig" and got proper compile.
Signed-off-by: Jiri Olsa <olsajiri@gmail.com>
---
fs/char_dev.c | 1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/fs/char_dev.c b/fs/char_dev.c
index c3bfa76..e4527fb 100644
--- a/fs/char_dev.c
+++ b/fs/char_dev.c
@@ -55,7 +55,6 @@ static struct char_device_struct {
unsigned int baseminor;
int minorct;
char name[64];
- struct file_operations *fops;
struct cdev *cdev; /* will die */
} *chrdevs[CHRDEV_MAJOR_HASH_SIZE];
next reply other threads:[~2008-02-20 20:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-20 20:57 Jiri Olsa [this message]
2008-02-21 0:15 ` [PATCH] fs: removing unused fops from struct char_device_struct Greg KH
2008-02-21 6:08 ` Jiri Olsa
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=47BC9433.8020905@gmail.com \
--to=olsajiri@gmail.com \
--cc=gregkh@suse.de \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@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