From: re.emese@gmail.com
To: linux-kernel@vger.kernel.org
Cc: Emese Revfy <re.emese@gmail.com>,
akpm@linux-foundation.org, mingo@elte.hu, matthew@wil.cx,
torvalds@linux-foundation.org
Subject: [PATCH 1/1] Constify struct file_lock_operations for 2.6.32-git-053fe57ac v2
Date: Mon, 14 Dec 2009 00:59:34 +0100 [thread overview]
Message-ID: <482ce9967027b3ce51ca7e1e38f024fd4eab9169.1260662997.git.re.emese@gmail.com> (raw)
In-Reply-To: <cover.1260662997.git.re.emese@gmail.com>
From: Emese Revfy <re.emese@gmail.com>
Signed-off-by: Emese Revfy <re.emese@gmail.com>
---
include/linux/fs.h | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/linux/fs.h b/include/linux/fs.h
index a057f48..c88cb4b 100644
--- a/include/linux/fs.h
+++ b/include/linux/fs.h
@@ -1028,8 +1028,8 @@ static inline int file_check_writeable(struct file *filp)
typedef struct files_struct *fl_owner_t;
struct file_lock_operations {
- void (*fl_copy_lock)(struct file_lock *, struct file_lock *);
- void (*fl_release_private)(struct file_lock *);
+ void (* const fl_copy_lock)(struct file_lock *, struct file_lock *);
+ void (* const fl_release_private)(struct file_lock *);
};
struct lock_manager_operations {
--
1.6.5.3
next prev parent reply other threads:[~2009-12-14 0:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-13 23:59 [PATCH 0/9] Constify struct file_operations " re.emese
2009-12-13 23:59 ` [PATCH 2/9] " re.emese
2009-12-13 23:59 ` [PATCH 3/9] " re.emese
2009-12-13 23:59 ` [PATCH 4/9] " re.emese
2009-12-13 23:59 ` [PATCH 5/9] " re.emese
2009-12-13 23:59 ` [PATCH 6/9] " re.emese
2009-12-13 23:59 ` re.emese [this message]
2009-12-13 23:59 ` [PATCH 7/9] " re.emese
2009-12-13 23:59 ` [PATCH 8/9] " re.emese
2009-12-13 23:59 ` [PATCH 9/9] " re.emese
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=482ce9967027b3ce51ca7e1e38f024fd4eab9169.1260662997.git.re.emese@gmail.com \
--to=re.emese@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®