public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH] xfs: remove xfs_buf_t typedef
Date: Thu, 17 Dec 2020 13:51:22 +1100	[thread overview]
Message-ID: <20201217025122.GO632069@dread.disaster.area> (raw)
In-Reply-To: <20201217003854.GD6918@magnolia>

On Wed, Dec 16, 2020 at 04:38:54PM -0800, Darrick J. Wong wrote:
> From: Dave Chinner <dchinner@redhat.com>
> 
> Prepare for kernel xfs_buf  alignment by getting rid of the
> xfs_buf_t typedef from userspace.
> 
> Signed-off-by: Dave Chinner <dchinner@redhat.com>
> [darrick: port the kernel now the 5.11 stuff has stabilized]
> Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> ---
>  fs/xfs/libxfs/xfs_alloc.c    |   16 ++++++++--------
>  fs/xfs/libxfs/xfs_bmap.c     |    6 +++---
>  fs/xfs/libxfs/xfs_btree.c    |   10 +++++-----
>  fs/xfs/libxfs/xfs_ialloc.c   |    4 ++--
>  fs/xfs/libxfs/xfs_rtbitmap.c |   22 +++++++++++-----------
>  fs/xfs/xfs_buf.c             |   24 ++++++++++++------------
>  fs/xfs/xfs_buf.h             |   14 +++++++-------
>  fs/xfs/xfs_buf_item.c        |    4 ++--
>  fs/xfs/xfs_fsops.c           |    2 +-
>  fs/xfs/xfs_log_recover.c     |    8 ++++----
>  fs/xfs/xfs_rtalloc.c         |   20 ++++++++++----------
>  fs/xfs/xfs_rtalloc.h         |    4 ++--
>  fs/xfs/xfs_symlink.c         |    4 ++--
>  fs/xfs/xfs_trans.c           |    2 +-
>  fs/xfs/xfs_trans_buf.c       |   16 ++++++++--------
>  15 files changed, 78 insertions(+), 78 deletions(-)

LGTM.

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

      reply	other threads:[~2020-12-17  2:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-17  0:38 [PATCH] xfs: remove xfs_buf_t typedef Darrick J. Wong
2020-12-17  2:51 ` Dave Chinner [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=20201217025122.GO632069@dread.disaster.area \
    --to=david@fromorbit.com \
    --cc=darrick.wong@oracle.com \
    --cc=linux-xfs@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