From: Carlos Maiolino <cmaiolino@redhat.com>
To: linux-xfs@vger.kernel.org
Subject: [PATCH 0/4] Remove a few macros
Date: Tue, 6 Mar 2018 14:00:49 +0100 [thread overview]
Message-ID: <20180306130053.13958-1-cmaiolino@redhat.com> (raw)
For a while, these macros have been removed from kernel, removing them from
xfsprogs brings the code closer to kernel code, and is a first step on such
process.
I tried to get rid of such macros as more segmented as possible (1 macro per
patch), although, last to patches are good candidates to be merged together, but
I believe it's just cleaner to have them as separated patches
Carlos Maiolino (4):
Get rid of XFS_BUF_PTR() macro
Get rid of XFS_BUF_TARGET() macro
get rid of XFS_BUF_COUNT() macro
Get rid of XFS_BUF_SET_COUNT() macro
libxfs/libxfs_io.h | 6 +-----
libxfs/logitem.c | 2 +-
libxfs/rdwr.c | 6 +++---
libxfs/trans.c | 2 +-
libxlog/xfs_log_recover.c | 2 +-
logprint/log_print_all.c | 4 ++--
mkfs/proto.c | 8 ++++----
mkfs/xfs_mkfs.c | 14 +++++++-------
repair/agheader.c | 6 +++---
repair/attr_repair.c | 4 ++--
repair/dino_chunks.c | 2 +-
repair/phase6.c | 4 ++--
repair/prefetch.c | 4 ++--
13 files changed, 30 insertions(+), 34 deletions(-)
--
2.14.3
next reply other threads:[~2018-03-06 13:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 13:00 Carlos Maiolino [this message]
2018-03-06 13:00 ` [PATCH 1/4] Get rid of XFS_BUF_PTR() macro Carlos Maiolino
2018-03-06 22:22 ` Dave Chinner
2018-03-07 6:12 ` Carlos Maiolino
2018-03-08 8:15 ` Christoph Hellwig
2018-03-06 13:00 ` [PATCH 2/4] Get rid of XFS_BUF_TARGET() macro Carlos Maiolino
2018-03-08 8:15 ` Christoph Hellwig
2018-03-06 13:00 ` [PATCH 3/4] get rid of XFS_BUF_COUNT() macro Carlos Maiolino
2018-03-08 8:15 ` Christoph Hellwig
2018-03-06 13:00 ` [PATCH 4/4] Get rid of XFS_BUF_SET_COUNT() macro Carlos Maiolino
2018-03-08 8:16 ` Christoph Hellwig
2018-03-08 13:23 ` Carlos Maiolino
2018-03-14 13:05 ` [PATCH 0/4] Remove a few macros Carlos Maiolino
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=20180306130053.13958-1-cmaiolino@redhat.com \
--to=cmaiolino@redhat.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;
as well as URLs for NNTP newsgroup(s).