From: tristan <tristan.ye@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 1/2] Ocfs2: Move ocfs2 ioctl definitions from ocfs2_fs.h to new added ocfs2_ioctl.h.
Date: Tue, 02 Mar 2010 10:08:04 +0800 [thread overview]
Message-ID: <4B8C7304.8070108@oracle.com> (raw)
In-Reply-To: <20100302012121.GC447@mail.oracle.com>
Joel Becker wrote:
> On Wed, Feb 24, 2010 at 03:51:11PM +0800, Tiger Yang wrote:
>
>> diff --git a/fs/ocfs2/file.h b/fs/ocfs2/file.h
>> index d66cf4f..eb891db 100644
>> --- a/fs/ocfs2/file.h
>> +++ b/fs/ocfs2/file.h
>> @@ -26,6 +26,8 @@
>> #ifndef OCFS2_FILE_H
>> #define OCFS2_FILE_H
>>
>> +#include "ocfs2_ioctl.h"
>>
>
> I wanted to grab this for the merge window, but I see that
> file.h is still including the new header. The header should be included
> in the appropriate C file, not here. Please clean this up.
>
Currently 'resize.h' and 'file.h' are using ioctl structures from
'ocfs2_ioctl.h', don't like 'resize.h', which only was included in
'resize.c', 'file.h' instead was referred everywhere:
fs/ocfs2/quota_global.c:22:#include "file.h"
fs/ocfs2/dir.c:56:#include "file.h"
fs/ocfs2/locks.c:35:#include "file.h"
fs/ocfs2/aops.c:41:#include "file.h"
fs/ocfs2/inode.c:45:#include "file.h"
fs/ocfs2/symlink.c:49:#include "file.h"
fs/ocfs2/mmap.c:42:#include "file.h"
fs/ocfs2/dcache.c:39:#include "file.h"
fs/ocfs2/file.c:51:#include "file.h"
fs/ocfs2/namei.c:55:#include "file.h"
fs/ocfs2/alloc.c:48:#include "file.h"
fs/ocfs2/ioctl.c:18:#include "file.h"
fs/ocfs2/xattr.c:47:#include "file.h"
fs/ocfs2/quota_local.c:17:#include "file.h"
fs/ocfs2/dlmglue.c:47:#include "file.h"
fs/ocfs2/acl.c:32:#include "file.h"
We therefore need to add 'ocfs2_ioctl.h' in many C sources to avoid
compile warnings.
Does it worth doing this? or maybe we can just add the 'ocfs2_ioctl.h'
into 'ocfs2.h', the downside is, it may cause some innocent sources
start including this undesired header.
Regards,
Tristan
>
> Joel
>
>
next prev parent reply other threads:[~2010-03-02 2:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 7:51 [Ocfs2-devel] [PATCH 1/2] Ocfs2: Move ocfs2 ioctl definitions from ocfs2_fs.h to new added ocfs2_ioctl.h Tiger Yang
2010-02-24 7:51 ` [Ocfs2-devel] [PATCH 2/2] Ocfs2: Add new OCFS2_IOC_INFO ioctl for ocfs2 v6 Tiger Yang
2010-03-02 1:21 ` [Ocfs2-devel] [PATCH 1/2] Ocfs2: Move ocfs2 ioctl definitions from ocfs2_fs.h to new added ocfs2_ioctl.h Joel Becker
2010-03-02 2:08 ` tristan [this message]
2010-03-02 2:32 ` Joel Becker
2010-03-02 3:13 ` tristan
2010-03-02 3:29 ` Joel Becker
2010-03-02 3:32 ` tristan
-- strict thread matches above, loose matches on Subject: below --
2010-02-08 9:21 Tristan Ye
2010-02-17 6:10 ` Joel Becker
2010-02-05 9:59 Tristan Ye
2010-01-08 8:51 Tristan Ye
2010-02-05 23:09 ` Joel Becker
2010-02-08 2:24 ` tristan
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=4B8C7304.8070108@oracle.com \
--to=tristan.ye@oracle.com \
--cc=ocfs2-devel@oss.oracle.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.