From: David Sterba <dsterba@suse.cz>
To: Alexandru Moise <00moses.alexander00@gmail.com>
Cc: clm@fb.com, jbacik@fb.com, dsterba@suse.com,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
holger.hoffstaette@googlemail.com
Subject: Re: [PATCH 1/2] btrfs: avoid passing int param to start_transaction which takes u64
Date: Tue, 22 Sep 2015 15:09:33 +0200 [thread overview]
Message-ID: <20150922130933.GD12815@twin.jikos.cz> (raw)
In-Reply-To: <20150913184720.GA25846@gmail.com>
On Sun, Sep 13, 2015 at 06:47:20PM +0000, Alexandru Moise wrote:
> Signed-off-by: Alexandru Moise <00moses.alexander00@gmail.com>
> ---
> v2: Forgot to add transaction.h when I made the commit, many thanks
> Holger for pointing it out.
>
> fs/btrfs/transaction.c | 2 +-
> fs/btrfs/transaction.h | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/btrfs/transaction.c b/fs/btrfs/transaction.c
> index 8f259b3..8a83acd 100644
> --- a/fs/btrfs/transaction.c
> +++ b/fs/btrfs/transaction.c
> @@ -570,7 +570,7 @@ reserve_fail:
> }
>
> struct btrfs_trans_handle *btrfs_start_transaction(struct btrfs_root *root,
> - int num_items)
> + u64 num_items)
I think it's better to do it the other way around, ie. let all the
equivalents of 'num_items' be an int. We know that this is a small
number, using u64 for that is an overkill. As the number is always
positive, please make it 'unsigned'.
next prev parent reply other threads:[~2015-09-22 13:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-13 18:47 Alexandru Moise
2015-09-22 13:09 ` David Sterba [this message]
2015-09-22 13:33 ` Alexandru Moise
2015-09-22 13:43 ` David Sterba
-- strict thread matches above, loose matches on Subject: below --
2015-09-13 14:29 Alexandru Moise
2015-09-13 14:53 ` Holger Hoffstätte
2015-09-13 18:34 ` Alexandru Moise
2015-09-13 18:50 ` Alexandru Moise
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=20150922130933.GD12815@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=00moses.alexander00@gmail.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=holger.hoffstaette@googlemail.com \
--cc=jbacik@fb.com \
--cc=linux-btrfs@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
all inboxes | Powered by JetHome®