linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.com>
Subject: [PATCH 0/4] Btrfs-progs 4.8, fix build on 32bit, ioctl cleanups
Date: Thu,  6 Oct 2016 15:41:37 +0200	[thread overview]
Message-ID: <20161006134141.837-1-dsterba@suse.com> (raw)

So this series should fix the 32bit build problems, tested on gcc 6.2.1. I've
added test of checking the ioctl numbers: "make test-ioctl" that will build
32bit and 64bit versions (needs compiler for both).

The ioctl compatibility reasoning is in the changelogs. The goal is to keep
everything working (send, receive), so there's no visible change, but more
testing would be welcome of course.

The patchset is now in devel, on top of 4.8.

David Sterba (4):
  btrfs-progs: ioctl: pack structures
  btrfs-progs: ioctl: add 32bit compat for SET_RECEIVED_SUBVOL
  btrfs-progs: ioctl: add 64bit compat for SEND
  btrfs-progs: tests: make the ioctl-test actually useful

 Makefile.in  |  27 +++++-
 ioctl-test.c | 266 +++++++++++++++++++++++++++++++++++++++++++++++++++++------
 ioctl.h      |  79 ++++++++++++++++--
 3 files changed, 335 insertions(+), 37 deletions(-)

-- 
2.10.0


             reply	other threads:[~2016-10-06 13:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-06 13:41 David Sterba [this message]
2016-10-06 13:41 ` [PATCH 1/4] btrfs-progs: ioctl: pack structures David Sterba
2016-10-06 13:41 ` [PATCH 2/4] btrfs-progs: ioctl: add 32bit compat for SET_RECEIVED_SUBVOL David Sterba
2016-10-06 13:41 ` [PATCH 3/4] btrfs-progs: ioctl: add 64bit compat for SEND David Sterba
2016-10-06 13:41 ` [PATCH 4/4] btrfs-progs: tests: make the ioctl-test actually useful 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=20161006134141.837-1-dsterba@suse.com \
    --to=dsterba@suse.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).