linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Vyacheslav Dubeyko <slava@dubeyko.com>
Cc: Hin-Tak Leung <htl10@users.sourceforge.net>,
	saproj@gmail.com, linux-fsdevel@vger.kernel.org, aia21@cam.ac.uk,
	viro@zeniv.linux.org.uk, hch@infradead.org, kalaracey@gmail.com
Subject: Re: [PATCH] hfsplus: fix "unused node is not erased" error
Date: Thu, 22 May 2014 00:07:57 -0700	[thread overview]
Message-ID: <20140522000757.7d8cdad4.akpm@linux-foundation.org> (raw)
In-Reply-To: <1400740185.2427.5.camel@slavad-CELSIUS-H720>

On Thu, 22 May 2014 10:29:45 +0400 Vyacheslav Dubeyko <slava@dubeyko.com> wrote:

> On Wed, 2014-05-21 at 21:12 +0100, Hin-Tak Leung wrote:
> 
> [snip]
> > >> diff --git a/fs/hfsplus/hfsplus_fs.h b/fs/hfsplus/hfsplus_fs.h
> > >> index 83dc292..3c872b2 100644
> > >> --- a/fs/hfsplus/hfsplus_fs.h
> > >> +++ b/fs/hfsplus/hfsplus_fs.h
> > >> @@ -417,6 +417,7 @@ void hfs_bnode_free(struct hfs_bnode *);
> > >>  struct hfs_bnode *hfs_bnode_create(struct hfs_btree *, u32);
> > >>  void hfs_bnode_get(struct hfs_bnode *);
> > >>  void hfs_bnode_put(struct hfs_bnode *);
> > >> +bool hfs_bnode_need_zeroout(struct hfs_btree *);
> > >>  
> > >>  /* brec.c */
> > >>  u16 hfs_brec_lenoff(struct hfs_bnode *, u16, u16 *);
> > >> @@ -463,7 +464,7 @@ int hfsplus_ext_write_extent(struct inode *);
> > >>  int hfsplus_get_block(struct inode *, sector_t, struct buffer_head *, int);
> > >>  int hfsplus_free_fork(struct super_block *, u32,
> > >>  		struct hfsplus_fork_raw *, int);
> > >> -int hfsplus_file_extend(struct inode *);
> > >> +int hfsplus_file_extend(struct inode *, bool zeroout);
> > >
> > >I think that it doesn't make sense to keep name of second argument here.
> > > 
> > >Thanks,
> > >Vyacheslav Dubeyko.
> > >
> > >
> > 
> > I disagree - I think 
> > If you are expanding the function prototype, you could also give the first argument some meaningful name while you are at it? 
> > 
> 
> To be honest, I don't quite follow your remark. I mean really simple
> thing here. It makes sense to have here the prototype with names for
> both arguments:
> 
> int hfsplus_file_extend(struct inode *inode, bool zeroout);
> 
> or without names of arguments:
> 
> int hfsplus_file_extend(struct inode *, bool);
> 
> Mixed declaration looks really weird for my taste. Moreover, most of
> prototypes are declared without names of arguments.
> 

Yes, mixed is weird.

I personally prefer that the names be included - if you ever actually
have to *read* one of these declarations it can be quite maddening when
they are omitted.


  reply	other threads:[~2014-05-22  7:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-21 20:12 [PATCH] hfsplus: fix "unused node is not erased" error Hin-Tak Leung
2014-05-22  6:29 ` Vyacheslav Dubeyko
2014-05-22  7:07   ` Andrew Morton [this message]
2014-05-22 12:48     ` Sergei Antonov
2014-05-22 13:13       ` Vyacheslav Dubeyko
2014-05-22 13:25         ` Sergei Antonov
2014-05-22 14:55           ` Vyacheslav Dubeyko
2014-05-22 17:35             ` Sergei Antonov
  -- strict thread matches above, loose matches on Subject: below --
2014-05-20 17:44 Sergei Antonov
2014-05-21 16:40 ` Vyacheslav Dubeyko
2014-05-21 18:15   ` Sergei Antonov
2014-05-22 13:07     ` Vyacheslav Dubeyko
2014-05-22 13:18       ` Sergei Antonov
2014-05-23  6:21         ` Vyacheslav Dubeyko
2014-05-23 10:54           ` Sergei Antonov

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=20140522000757.7d8cdad4.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=aia21@cam.ac.uk \
    --cc=hch@infradead.org \
    --cc=htl10@users.sourceforge.net \
    --cc=kalaracey@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=saproj@gmail.com \
    --cc=slava@dubeyko.com \
    --cc=viro@zeniv.linux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).