linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Mason <clm@fb.com>
To: Omar Sandoval <osandov@osandov.com>, <linux-btrfs@vger.kernel.org>
Cc: Chris Murphy <lists@colorremedies.com>,
	Andreas Gruenbacher <agruenba@redhat.com>,
	<stable@vger.kernel.org>, <kernel-team@fb.com>
Subject: Re: [PATCH v2 0/3] Btrfs: disable xattr operations on subvolume directories
Date: Thu, 26 Jan 2017 18:45:54 -0500	[thread overview]
Message-ID: <dcadede8-59ec-7ed8-12e7-9d3f9a71e37d@fb.com> (raw)
In-Reply-To: <cover.1485392101.git.osandov@fb.com>

On 01/25/2017 08:06 PM, Omar Sandoval wrote:
> From: Omar Sandoval <osandov@fb.com>
>
> This series is based on v4.10-rc4. It should probably go in for v4.10
> and to stable for v4.9.x.

Thanks Omar, I've got this queued on top of Dave's pull.

-chris

  parent reply	other threads:[~2017-01-26 23:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-26  1:06 [PATCH] Btrfs: disable xattr operations on subvolume directories Omar Sandoval
2017-01-25  2:38 ` Omar Sandoval
2017-01-25 12:28 ` Andreas Gruenbacher
     [not found]   ` <CAHc6FU7ubp4-A-oF+0nuKf27QJMeG_UtQx0pjdL7uVS+UwX6uw@mail.gmail.com>
2017-01-25 23:46     ` Omar Sandoval
2017-01-26  1:06 ` [PATCH v2 0/3] " Omar Sandoval
2017-01-26  1:06   ` [PATCH v2 1/3] Btrfs: remove old tree_root case in btrfs_read_locked_inode() Omar Sandoval
2017-01-26 17:19     ` David Sterba
2017-01-26  1:06   ` [PATCH v2 2/3] Btrfs: disable xattr operations on subvolume directories Omar Sandoval
2017-01-26 17:19     ` David Sterba
2017-01-26  1:06   ` [PATCH v2 3/3] Btrfs: remove ->{get,set}_acl() from btrfs_dir_ro_inode_operations Omar Sandoval
2017-01-26 17:18     ` David Sterba
2017-01-26 23:45   ` Chris Mason [this message]
2017-01-26  1:08 ` [PATCH] Btrfs: disable xattr operations on subvolume directories Omar Sandoval

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=dcadede8-59ec-7ed8-12e7-9d3f9a71e37d@fb.com \
    --to=clm@fb.com \
    --cc=agruenba@redhat.com \
    --cc=kernel-team@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.com \
    --cc=osandov@osandov.com \
    --cc=stable@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).