From: David Sterba <dsterba@suse.cz>
To: Hans van Kranenburg <hans.van.kranenburg@mendix.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs: use the correct struct for BTRFS_IOC_LOGICAL_INO
Date: Mon, 4 Jul 2016 19:57:08 +0200 [thread overview]
Message-ID: <20160704175708.GO13336@twin.jikos.cz> (raw)
In-Reply-To: <1467580986-2968-1-git-send-email-hans.van.kranenburg@mendix.com>
On Sun, Jul 03, 2016 at 11:23:06PM +0200, Hans van Kranenburg wrote:
> BTRFS_IOC_LOGICAL_INO takes a btrfs_ioctl_logical_ino_args as argument,
> not a btrfs_ioctl_ino_path_args. The lines were probably copy/pasted
> when the code was written.
>
> Since btrfs_ioctl_logical_ino_args and btrfs_ioctl_ino_path_args have
> the same size, the actual IOCTL definition here does not change.
>
> But, it makes the code less confusing for the reader.
>
> Signed-off-by: Hans van Kranenburg <hans.van.kranenburg@mendix.com>
Reviewed-by: David Sterba <dsterba@suse.com>
prev parent reply other threads:[~2016-07-04 17:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-03 21:23 [PATCH] Btrfs: use the correct struct for BTRFS_IOC_LOGICAL_INO Hans van Kranenburg
2016-07-04 17:57 ` David Sterba [this message]
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=20160704175708.GO13336@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=hans.van.kranenburg@mendix.com \
--cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).