From: Artem Bityutskiy <dedekind1@gmail.com>
To: Sedat Dilek <sedat.dilek@googlemail.com>
Cc: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
Sedat Dilek <sedat.dilek@gmail.com>,
Adrian Hunter <adrian.hunter@nokia.com>,
Jens Axboe <jaxboe@fusionio.com>
Subject: Re: [PATCH] ubifs: Use empty_iops and empty_fops consistently
Date: Mon, 04 Apr 2011 10:04:16 +0300 [thread overview]
Message-ID: <1301900656.2760.6.camel@localhost> (raw)
In-Reply-To: <1301874939-2630-1-git-send-email-sedat.dilek@gmail.com>
On Mon, 2011-04-04 at 01:55 +0200, Sedat Dilek wrote:
> Follow the nomenclature as we did for empty_aops and rename
> to empty_iops and empty_fops.
>
> This patch is on top of linux-2.6-block.git#for-linus.
>
> Signed-off-by: Sedat Dilek <sedat.dilek@gmail.com>
> CC: Artem Bityutskiy <dedekind1@gmail.com>
> CC: Adrian Hunter <adrian.hunter@nokia.com>
> CC: Jens Axboe <jaxboe@fusionio.com>
> ---
> fs/ubifs/xattr.c | 8 ++++----
> 1 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/fs/ubifs/xattr.c b/fs/ubifs/xattr.c
> index 3299f46..16f19f5 100644
> --- a/fs/ubifs/xattr.c
> +++ b/fs/ubifs/xattr.c
> @@ -80,8 +80,8 @@ enum {
> SECURITY_XATTR,
> };
>
> -static const struct inode_operations none_inode_operations;
> -static const struct file_operations none_file_operations;
> +static const struct inode_operations empty_iops;
> +static const struct file_operations empty_fops;
>
> /**
> * create_xattr - create an extended attribute.
> @@ -131,8 +131,8 @@ static int create_xattr(struct ubifs_info *c, struct inode *host,
>
> /* Re-define all operations to be "nothing" */
> inode->i_mapping->a_ops = &empty_aops;
> - inode->i_op = &none_inode_operations;
> - inode->i_fop = &none_file_operations;
> + inode->i_op = &empty_iops;
> + inode->i_fop = &empty_fops;
>
> inode->i_flags |= S_SYNC | S_NOATIME | S_NOCMTIME | S_NOQUOTA;
> ui = ubifs_inode(inode);
Well, this re-naming looks strange for me. I could understand if you had
a global exported empty_*ops which you could share and shrink the .data
size a bit. But this re-naming just looks useles, if you take into
account the breakage and the men-hours we spend to write e-mails to this
thread - really did not worth it. Or I miss something?
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2011-04-04 7:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-03 23:55 [PATCH] ubifs: Use empty_iops and empty_fops consistently Sedat Dilek
2011-04-04 7:04 ` Artem Bityutskiy [this message]
2011-04-04 9:38 ` Sedat Dilek
2011-04-04 10:06 ` Artem Bityutskiy
2011-04-04 10:29 ` Sedat Dilek
2011-04-19 9:50 ` Sedat Dilek
2011-04-19 10:02 ` Artem Bityutskiy
2011-04-19 10:21 ` Sedat Dilek
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=1301900656.2760.6.camel@localhost \
--to=dedekind1@gmail.com \
--cc=adrian.hunter@nokia.com \
--cc=jaxboe@fusionio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=sedat.dilek@gmail.com \
--cc=sedat.dilek@googlemail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox