From: Liu Bo <bo.li.liu@oracle.com>
To: dsterba@suse.cz, Stefan Behrens <sbehrens@giantdisaster.de>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [RFC PATCH] Btrfs: change ioctl number of BTRFS_IOC_START_SYNC to 21
Date: Thu, 7 Nov 2013 21:45:25 +0800 [thread overview]
Message-ID: <20131107134524.GA9760@localhost.localdomain> (raw)
In-Reply-To: <20131106132425.GV16662@twin.jikos.cz>
On Wed, Nov 06, 2013 at 02:24:25PM +0100, David Sterba wrote:
> On Wed, Nov 06, 2013 at 10:42:35AM +0100, Stefan Behrens wrote:
> > Sharing the ioctl value seems to have happened by mistake and is
> > uncommon, but IMHO now it's too late to change this interface just for
> > esthetical reasons.
>
> Agreed, it's part of ABI, ioctl.h is "append only".
Ok, I think that's why I tagged it as 'RFC' :-)
-liubo
prev parent reply other threads:[~2013-11-07 13:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 9:01 [RFC PATCH] Btrfs: change ioctl number of BTRFS_IOC_START_SYNC to 21 Liu Bo
2013-11-06 9:42 ` Stefan Behrens
2013-11-06 13:24 ` David Sterba
2013-11-07 13:45 ` Liu Bo [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=20131107134524.GA9760@localhost.localdomain \
--to=bo.li.liu@oracle.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=sbehrens@giantdisaster.de \
/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).