From: David Sterba <dsterba@suse.cz>
To: Sahil Kang <sahil.kang@asilaycomputing.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 1/1] btrfs: reuse existing inode from btrfs_ioctl
Date: Mon, 17 Jan 2022 14:39:21 +0100 [thread overview]
Message-ID: <20220117133921.GF14046@twin.jikos.cz> (raw)
In-Reply-To: <20220116024847.29047-2-sahil.kang@asilaycomputing.com>
On Sat, Jan 15, 2022 at 06:48:47PM -0800, Sahil Kang wrote:
> btrfs_ioctl extracts inode from file so we can pass that into the
> subfunctions.
>
> Signed-off-by: Sahil Kang <sahil.kang@asilaycomputing.com>
Added to devel, thanks.
> -static int _btrfs_ioctl_send(struct file *file, void __user *argp, bool compat)
> +static int _btrfs_ioctl_send(struct inode *inode,
> + void __user *argp,
> + bool compat)
Please keep the lines filled and don't split when not necessary. Fixed
in the committed patch.
next prev parent reply other threads:[~2022-01-17 13:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 8:30 [PATCH 0/1] btrfs: reuse existing pointers from btrfs_ioctl Sahil Kang
2022-01-05 8:30 ` [PATCH 1/1] " Sahil Kang
2022-01-05 9:53 ` Qu Wenruo
2022-01-06 15:03 ` David Sterba
2022-01-16 2:48 ` [PATCH 0/1] btrfs: reuse existing inode " Sahil Kang
2022-01-16 2:48 ` [PATCH 1/1] " Sahil Kang
2022-01-17 13:39 ` David Sterba [this message]
2022-01-06 15:27 ` [PATCH 1/1] btrfs: reuse existing pointers " David Sterba
2022-01-05 9:30 ` [PATCH 0/1] " Qu Wenruo
2022-01-06 15:11 ` David Sterba
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=20220117133921.GF14046@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=sahil.kang@asilaycomputing.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.