linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Goffredo Baroncelli <kreijack@libero.it>
To: Filipe David Borba Manana <fdmanana@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [RFC PATCH] Btrfs: add support for inode properties
Date: Tue, 12 Nov 2013 20:24:33 +0100	[thread overview]
Message-ID: <52828071.8090305@libero.it> (raw)
In-Reply-To: <1384263757-25627-1-git-send-email-fdmanana@gmail.com>

Hi Filipe,

On 2013-11-12 14:42, Filipe David Borba Manana wrote:
> This change adds infrastructure to allow for generic properties for
> inodes via a new ioctl. 

I am sure that there is a valid reason, but I was not able to find it:
why implement a new ioctl instead of using the *{set,get)xattr(2) syscall ?

I noticed that you implemented the Compression properties set/get: is
this from "chattr -c" ?

[... cut other lines ... ]

G.Baroncelli

-- 
gpg @keyserver.linux.it: Goffredo Baroncelli (kreijackATinwind.it>
Key fingerprint BBF5 1610 0B64 DAC6 5F7D  17B2 0EDA 9B37 8B82 E0B5

  reply	other threads:[~2013-11-12 19:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-12 13:42 [RFC PATCH] Btrfs: add support for inode properties Filipe David Borba Manana
2013-11-12 19:24 ` Goffredo Baroncelli [this message]
2013-11-12 20:04   ` Filipe David Manana
2013-11-12 20:07     ` Hugo Mills
2013-11-13  0:30       ` Filipe David Manana
2013-11-13  1:21 ` [PATCH V2] " Filipe David Borba Manana
2013-11-13 18:59   ` Goffredo Baroncelli
2013-11-19 16:06     ` Filipe David Manana
2013-11-19 17:44       ` Goffredo Baroncelli
2013-11-19 16:00 ` [PATCH v3] " Filipe David Borba Manana
2014-01-07 11:47 ` [RFC PATCH v4] " Filipe David Borba Manana

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=52828071.8090305@libero.it \
    --to=kreijack@libero.it \
    --cc=fdmanana@gmail.com \
    --cc=kreijack@inwind.it \
    --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).