public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Eric Sandeen <sandeen@redhat.com>, xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] xfs: hide the XFS_IOC_{ALLOC,FREE}SP* definitions
Date: Tue, 11 Jan 2022 08:10:01 +1100	[thread overview]
Message-ID: <20220110211001.GA945095@dread.disaster.area> (raw)
In-Reply-To: <20220110195854.GY656707@magnolia>

On Mon, Jan 10, 2022 at 11:58:54AM -0800, Darrick J. Wong wrote:
> From: Darrick J. Wong <djwong@kernel.org>
> 
> Now that we've made these ioctls defunct, move them from xfs_fs.h to
> xfs_ioctl.c, which effectively removes them from the publicly supported
> ioctl interfaces for XFS.
> 
> Signed-off-by: Darrick J. Wong <djwong@kernel.org>
> ---
> v2: nuke the 32-bit compat definitions too
> ---
>  fs/xfs/libxfs/xfs_fs.h |    8 ++++----
>  fs/xfs/xfs_ioctl.c     |    9 +++++++++
>  fs/xfs/xfs_ioctl32.h   |    4 ----
>  3 files changed, 13 insertions(+), 8 deletions(-)

Looks good to me.

Reviewed-by: Dave Chinner <dchinner@redhat.com>

-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2022-01-10 21:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-10 17:48 [PATCH 1/2] xfs: kill the XFS_IOC_{ALLOC,FREE}SP* ioctls Darrick J. Wong
2022-01-10 17:51 ` [PATCH 2/2] xfs: hide the XFS_IOC_{ALLOC,FREE}SP* definitions Darrick J. Wong
2022-01-10 18:39   ` Eric Sandeen
2022-01-10 19:59     ` Darrick J. Wong
2022-01-10 19:58   ` [PATCH v2 " Darrick J. Wong
2022-01-10 21:10     ` Dave Chinner [this message]
2022-01-11 16:24     ` Eric Sandeen
2022-01-10 18:37 ` [PATCH 1/2] xfs: kill the XFS_IOC_{ALLOC,FREE}SP* ioctls Eric Sandeen
2022-01-10 21:08 ` Dave Chinner
2022-01-18  2:26 ` [xfs] 270a6968dc: xfstests.xfs.009.fail kernel test robot

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=20220110211001.GA945095@dread.disaster.area \
    --to=david@fromorbit.com \
    --cc=djwong@kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sandeen@redhat.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